Friday, February 8th, 2013, Confessions of a Tester
When working on an Agile project each iteration must be completed before continuing onto the next. No matter what the nature of the work being carried out is, when something is considered as completed, it must really mean it is completed. Apart from having features that depend on others, each completed feature must be in a state that is ready to be deployed. The most common assumption is thinking that when the development part is done, the project is actually completed. The feature or module would not have been tested and styled in a way that the product owner or sponsor will accept it. It would only mean that the coding part is ready. How about testing it? What about the Read more »
Friday, January 11th, 2013, Confessions of a Tester
I was once involved in a project at an insurance company. The system we built was an insurance system for one of the largest insurance companies in the country. We had some hundreds of users spread across different locations over … Read more
Friday, September 14th, 2012, Newsletters
Acceptance testing is perhaps the most important of all test levels, as this is the time for users to let their voice be heard before deployment. Strangely, these tests are often not performed well enough. A common problem is communication between … Read more
Wednesday, September 21st, 2011, Blog, Newsletters
This article will give you 5 specific actions you can regard as a checklist for success in acceptance testing. Read more