Sample of an efficient, measurable process that is simple to use, adaptable and tool independent for managing defects found during product development.
The following process flow diagram provides an overview of the transitions of product defect status during the workflows during each stage during the life of a defect.
1. A defect is entered into the defect management tool by the defect finder.
A significant factor in a successful testing effort is how well the tests are written. They have to be effective in verifying that approved requirements have been met AND the test cases themselves are understandable so the tester can run the test as intended by the test author. A test case has to be easy to understand; is has to be smart! So, what makes a test case smart? It's not that it's been slapped! A test case is smart when it is:
Under Development (I'm updating content minute by minute, day by day. Some come back for more when you can.)
Do you have test cases currently kept in MS Word, MS Excel or other sources that you need to get into HP's Quality Center? Here's an approach I've used that has worked well for me. Build an Inventory
Collect all your existing test cases to a single location and create an MS Excel workbook to contain a list of all the test case names. Do not at this stage include the details of each test case.
At first glance they are like oil (Agile lubricates development by reducing resistance) and water (FDA drowns you in processes and paperwork); they just don’t mix well at all!
Agile de-emphasizes documentation, controls and tools in favor of close interaction between individuals working on small pieces of functionality without the overhead of detailed processes and documentation.
The FDA requires companies, under their jurisdiction, to comply with a mountain of published regulations and guidelines that cover the processes and documentation needed to qualify a product for release.
