Skip to main content

Posts

Showing posts from February, 2014

Ensure Effective Regression Testing in 5 Ways!

Regression testing is essential as it aims to find failures in the product after code changes, support of new environment or product release.

By regression testing you also ensure user confidence assessing if the product’s new version is better than the previous one. Although many companies still ignore its necessity and fail to run product tests after the release, this testing stage should not be overlooked. Below are 5 accepted ways to perform regression testing of your product.1. Run all existing tests
This means that all the tests written and run before should be rerun after the release. However, especially if they all are manual, testers are going to have a huge pile of work. Probably you don’t have that much time and resources to be wasted. The fact that it’s impossible to perform 100% overall testing of the product also adds to this. 2. Run tests with high risk
In this method you should take into consideration the tests presenting the most value to your business users. Mostly such t…

3 Things to a Remember While Doing Exploratory Testing!

Here is a post I found interesting... 

While doing exploratory testing it’s often difficult to decide what to start with since the opportunities abound.
In order to do it effectively we offer testers to concentrate on the three starting points to keep in mind all the way through. Don’t follow the documentation. Exploratory testing is something you can perform without any specification and scripted test cases. However, if such handy guides are at hand, it’s always tempting to resort to their instructions. This is the mindset you have to avoid. While checking in with the documentation, you tend to rely on their standpoints and assume the tactic of confirming that everything works as expected. Instead your role now is the opposite, because you have to find the points where the system fails. It’s better to do cross-reference using documentation afterwards. Without resorting to it you think broader, you may even unintentionally discover some undocumented implicit requirements, errors and incon…