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.
Someone recently asked me what resources I would recommend to a new .NET developer. I wish someone had given me some sort of advice as to which books are good, which ones to avoid, which sites to visit, and which ones to avoid. Well, below is my list of useful resources for new .NET developers.
Everyone has a story about how they came into being a professional software developer. Below is mine. I am writing this mainly for myself, but I hope you, dear reader, can gain something from it.
How It All Started
Before I made the choice to become a software developer, I was a music major at a local community college. It was my dream, then, to be a band director since I enjoyed teaching and performing on stage. I did well as a music major and was hesitant to switch over to computer science. Computer science was out of my comfort zone, and music was all I knew.
Some days are rough: having to deal with users that think they know it all, putting out fires, and having to deal with office politics, among other things. However, some days are very smooth and renew my faith in humanity. I think everyone, at any company, typically wants to do the best job they can (and then go home!). Continue reading
The Good Old Days
I remember the first time I wrote a single line of code. It was in MS-DOS 6.0 in QBASIC back in 1995 on my first computer. My first “Hello World” program was awesome. I could not help but feel a sense of power when I learned I could actually “tell” the computer what to do. Back in 1995 the internet was slow and programming resources were scarce or hard to find. I taught myself everything from the Help contents.
Each day I opened QBASIC was like an adventure. “What can I do today?” I would wonder. I remember teaching myself, and not quite understanding, arrays and data types. Continue reading