This is going to be a deep dive into the markup, or view, side of a page. If you recall in an earlier post, we took a very high level look at the different components that make up a page.
These pages allow you to enter special server-side controls, which can be modified or acted upon on the server, through a code behind file, typically.
Please note that this will not be a tutorial on how to use Visual Studio or how to File > New Project something. This will be an exploration into server controls in ASP.NET.
Tonight’s post is going to be short. I wanted to do a very basic overview of the different components of a web forms page.
A test case is a statement that describes what the test will be performing. A test script is part of a test case and are the granular steps to perform the test case. A test case should aim to exercise as much of a set of requirements as possible, while still being concise.
Formally, a test case is:
[A] set of conditions or variables under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do. [Wikipedia]
I started out in my career as a test automation engineer and manual software tester in Quality Assurance.
Testing is paramount to developing high quality software. The meme “I don’t always test my code, but when I do, I test in production” is funny but also, unfortunately, very true. It is rare to have a fully-functional QA team these days. Developers are expected to test their own code.