Articles

One of the important issues in software testing is the documentation of the tests, without documentation, it is not possible to know which situations have been tested, whether the process has been properly covered, whether all end-cases have been tested, are the testing priorities correct? On the basis of the famous saying "You did and did not report - did not do", it can be said: Tested and not documented = Not tested.

Several options for building a software testing team in the fast business world, Each business body makes adjustments to the company's objectives.

In the next two weeks, we are about to finalize tests, the fifth version this year, not including emergency transfers and "cross-version" failures and emergency repairs ...... which are required .... During the tests, bugs are discovered which are documented and passed to the development team.

The amount of test types is large, we have made a division by subject here to facilitate and make some order... Good luck.

The testing process consists of five basic steps: designing the test project, designing test scenarios, performing the tests, testing the documentation and meeting the threshold conditions for the completion of the tests.

The choice is yours: Walk in a long and hard way or discover shortcuts. Spend 4 years gathering slow information or establish a mechanism An effective method that operates in an understandable manner and creates optimal testing planning.

Creating a analysis report on-LINE test results must be available and accurate, because this report is critical to the decision to increase to PRODUCTION.

Root Cause Analysis-Coping with problems not only symptoms. Article presented in the USA at the STAR Conference In Orlando (2008), and at conferences in Europe (2008, 2009). and won a great feedback.

Many times I have been asked this question and many times I have asked it myself. Nine out of 10 times the answer was: when you reach a deadline or when the project manager decides. This is of course a real and real answer, but is it the answer that we as QA managers and examiners need to look for?

A list of software and aids for a reviewer on the subject: Load Testing Testing and planning management Bug Management Web Checks Embedded Systems