Various Thoughts about Software Testing

Measuring Stress

When stress testing software, it is desirable to know if the software is actually being stressed. To know this we must first define what is meant by stressed. For the purposes of testing, a system is stressed when the rate at which operation against a

Classes of Stress Tests

Stress is a common test category, but it can have different meanings depending on context and goals. Some stress tests are used to see how a system behaves under load. Others are used to generate random operations against the software to gain coverage

Why Automate

(Forgive the formatting of this post. Getting the code to be readable seems to be given me issues.) Reasons why to automate tests: 1. Laziness. Executed the same test over and over manually is boring. 2. Speed. Automation runs faster than a human. 3.

Test vs. Test Case

A common term in testing is test case. Unfortunately it doesn't have a single meaning. Instead it is viewed different depending on contest. My definition is fairly simple. A test case is the minimum unit of execution which performs a test. A test is a

Test Case Automation vs. Execution Automation

When talking about test automation, there are two different classes of automation that often come up. The first is the automation of a test case. This is the code/script which actually exercises the system being tested. The second is the automation of

Degrees of Test Automation

Welcome to the first entry in my discussion of test automation. I'll be starting by discussing the different levels of automation that can be applied to testing. Future posts will cover test case automation vs. execution automation, why automate tests,

Introductions

Greetings all. My name is Jacob Buis. I'm a Software Design Engineer in Test at Microsoft. I've been working on Windows and storage technology for the past eight years and I've decided that it would be a good idea to share some of my experiences and opinions