Most teams today use an inverted pyramid where most of the tests are manual User Acceptance Tests and System tests and are manually executed via the UI. Unit tests are non-existent or are too few to be beneficial. In order to have a maintainable test suite, as explained in this post, the base of our pyramid…

When trying to decide how to distribute our testing efforts and how many tests to write for each different type, it’s important to consider: Test coverage: How much of the code has a test that verifies its behaviorTest execution time: How long does it take to run the test and get a result backTest feedback: How…

When we look at the different types of tests and the Agile Testing Quadrant, which tests in which quadrant can we automate? In general, any tests that can be scripted can and should be automated. If we can map out a series of preparatory steps, followed by an action that results in an expected value or…

Brian Marick came up with a way to categorize the different types by 2 dimensions: Tests that support programming or the team and tests that critique the productTests that are technology facing and tests that are business facing Test that support the team: These are tests that help the team build and change the application with…

Test definitions vary. Sometimes they are categorized by type, level and approach. Below is my take on the different types of testing. Unit Testing: Verifies that a single unit of code (a specific behavior in a method) behaves as intended. Integration Testing: Verifies that two or more units communicating with each other behave as intended. Component…