Check out the video below of Michael Hamman presenting on "The Inner Game of Agility" at Washington DC Scrum User Group (DCSUG). Michael explores the nature of inner agility, which refers to the sensemaking, communication, and relationship intelligence of an organization’s people. How might we concretely define the realm of inner agility? Why is it important…
Testing is everyone’s responsibility. The entire team works collectively to develop a quality product. Most of the automation is done by the people writing the code using an approach known as Test Driven Development or Test Driven Design (TDD). This includes unit, integration, component, and system tests. These tests verify that the application works as intended.…
What does your task board say about your team? Many teams have a separate testing column. This indicates that we are still doing hand-offs from development to testing and that testing is an afterthought. Testing is not a phase that happens at the end of a project and it’s not a phase that happens at the…
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…
Merriam-Webster defines the word bug as "an unexpected defect, fault, flaw, or imperfection." In 1946, the 1st ever case of a software bug was reported in an early electro-mechanical computer called the Mark II. An actual moth got trapped in the relay of the computer and caused it to malfunction. The moth was removed and taped…
Check out the video below of Julie Wyman and Mark Grove presenting on "What's Really Going on? An Observational Workshop" at the Washington DC Scrum User Group (DCSUG). They show us how observation is a powerful tool, but one which we may not take advantage to its true potential. By learning how to expand our observational…
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…