This space is dedicated to the QA procedures and testings.

Current projects and status

These are the links to all test informations on the different projects.

Legend

"Awaiting new version": Testers have completed all tests on the last released version.
"Build Fails": The realeased build fails on our integration servers. Testing cannot continue without help from the project developers.
"Automated Tests Fail": Our suite of automated tests are failing. Testing cannot continue without help from the project developers.
"Testing in progress": The testing team is currently at work on the latest released version. During this time you will see new jira bugs appearing.

Resources

[Integration Test and Demo Servers ]

Projects life cycle

All our projects should follow the life cycle descibed in the link. It inclides the development but also the QA and documentation part.

For more visibility on the QA and projects life cycle, please follow the link.

Documentation templates:

These are the templates to be used for our projects. Clicking on them will download them on your machine.

Requirements

functional specifications

Test Plans (partially populated with a real example for better understanding)

Standards and procedures:

Since QA is involved in the early stages of the projects creation, it is important to normalize and standardize the life of the projects. Every member of the team is involved and it is important for all to read and be aware of the procedures and standards.

During the development phase, it is important for all developers to follow the QA PROCESS when they want a subversion/ a new release to be tested.

This in necessary to be able to keep track of what is happening, on which version and it will bring better results.

Using Jira/definitions

The bugs/defects are logged into Jira.

The processes and definitions are described here.

QA meetings:

The QA teams tries to keep minutes of their meetings on planning. These can be seen via this link.

Home