Hot answers tagged test-strategy
This is often a difficult argument, not least because it frequently shifts "test" responsibility to developers, who may not wish to deal with writing unit or integration tests and see no value to either. Some points I've found helpful here are: It's much cheaper in terms of licenses needed and time required to keep business logic tests at the unit test ...
In this situation, we are using the approach exposed by Bruce McLeod. We use a data generator to produce 4 datasets from the same configuration defined by the test case: the input data for the test (run manually or with qtp) to fill gui forms for example, the data inserted before test with soapui in the application to create the customers on which the ...
As the other answers have said, your first task is to organize the list. There are a number of reasons you want to do this: The items may not be accurate - This is ridiculously common. What tends to happen is that the people who execute the test steps know enough about the system to adjust for flaws in the list and act accordingly. The items may not be ...
As aspects are typically written to add behaviour to code, I would suggest that you'll need to indirectly test the functionality by creating a test object/method that'll be impacted by the aspect and then blackbox test the code at runtime for the behaviour you'd expect to be seeing.
Only top voted, non community-wiki answers of a minimum length are eligible