System test preparations
tammi 05

System test preparations

The purpose of System Testing is to ensure that the built-in functionality works technically correctly, supports the business needs and is suitable for a complete solution. The system testing, test cases are a tool in order to assure this.

The test cases of a system test have the following requirements:

  1. They must be business-oriented
  2. They must be able to report on their realization in real time.
  3. Test cases guide you to test high quality testing.
  4. Writing test cases should not take too long.
  5. Testing should be effective and it is effective.
  6. The setup of testing should be easy.
  7. The tester can get a clear list of test cases on My activities view and be able to do the right tests at the right time.

There are several requirements on the list, so you have to invest in writing test cases. Pinching pennies in writing causes major problems as the project progresses.

projecttop vip area - system test preparations - dependencies

Dependencies

Test cases for system testing are created based on use cases. Dependencies are created between documents. This creates the basis for reporting for system testing approval.

Test Preparation Process

projecttop vip area - system test preparations - Process

Timing

After the build packet is accepted for building, the vendor starts to build a solution according to the use case. At the same time the customer starts preparation of testing.

Generate test case steps from use case and modify those to “testing language”

Create steps of the first test scenario so that you copy the use case steps. After that change the language to “Testing language”.  This usually means command mode.

After that add Check-lines. Check-lines tell the tester to check the important points in the process that might otherwise go unnoticed.

projecttop vip area - system test preparations - List of test cases and resource planning

Generate test case steps from use case and modify those to “testing language”

Create steps of the first test scenario so that you copy the use case steps. After that change the language to “Testing language”.  This usually means command mode.

After that add Check-lines. Check-lines tell the tester to check the important points in the process that might otherwise go unnoticed.

projecttop vip area - system test preparations - Case steps
projecttop vip area - system test preparations - Chart

After you have done the first case, copy steps to the next one.

Make necessary changes and save.

projecttop vip area - system test preparations - Copy

Master data and test data

If you want to have a high quality test, you need high-quality master data. Building master data into a new system will take time, but testing with bad data will take even more time.

Data processing in projects depends on the nature of the project. That is why it has not been dealt with in depth in this documentation.

Technical environments and interfaces

Also technical and interface preparations depends on the nature of the project. A technical solution is required for testing, which corresponds to production use.

Vendor checks the test cases

After the test cases of one use case are ready, assign the cases to the vendor’s consultant. Vendor checks tests cases and adds the needed technical information.

This is very important, because errors in specifications are the most expensive errors. The price of errors is even more expensive, the later they are found. This way, errors are found already in the building phase. This will give the system and approval testing a better quality.

The vendor can also use these test cases as documentation for his own unit testing.

projecttop vip area - system test preparations - Vendor checks
projecttop vip area - system test preparations - Release

Release the case for testing

After one case is ready for testing, the vendor assigns the related test case to a test manager and changes the status to “Ready for testing”. This way we get real-time reporting about building readiness.

This is also important. Traditionally, up to 40% of the errors come from uncompleted implementation.  According to the Projecttop Process, you avoid these errors completely.

Jyrki Autio

CEO of Projecttop He’s often hired to save projects that are far behind schedule, are going over budget, or aren’t meeting quality standards. He also commonly trains people in specialist and consulting companies that sell project management or software development services.