This post is to discuss the QA Testing Process that is followed at Auro Infotech and generally recommended by us. QA Testing Process is one of the key items involved in any web development process.
QA Testing Process is embedded closely into our Auro Project Development Life Cycle model and hence is dependent on a few important parameters.
During the discussion process with any client for a new website development (or enhancement) we ask our clients some important questions related to QA testing of their website.
1. Which Operating Systems would you like your site to be tested on?
2. browsers would you like the site to be tested on?
3. Which versions of browsers would you like the site to be tested on?
4. Which display resolutions would you like the site to be tested on?
We facilitate this question with a simple spreadsheet (will post a copy of it here shortly).
For a typical website, the recommendation from Auro Infotech is something like:
1. Operating Systems: Windows and Mac
2. Browsers: Internet Explorer, FireFox, Safari, Chrome
3. Versions: IE 6, IE 7, FF2, FF3
4. Resolutions: 1024 by 768, 1200 by 800, 1600 by 1200.
In the past we have seen clients ask us to test on some things outside the above recommended list (eg. Mobile devices, 800 by 600, etc).
This baselining helps us to start the project with a clear understanding of the client expectations and helps us to plan the development better.
Every project has a major and minor version number using which each project is labeled.
We use the following format: Project Name v <Major Version Number> . <Minor Version Number>
Examples are given below:
– Weavez v1.0 (We typically use 1.0 if this is a brand new website we are developing).
– Floretz v2.0 (We typically use 2.0 if we get a website that is already built by some other team and we are taking it over)
– Flair Tours v1.1 (If a client asks for a minor change to be done to a website, we increase only the minor version and not the major version.)
– Music Plugin v2.5 (If it is a change that is not minor but not large enough to be called major, we just create a version .5 from the current version).
The team at Auro Infotech gets a better idea of the type of changes going on in any project from the minor version number.
QA Testing Cycle:
Our development team typically develops the applications and does their part of testing (called developer testing) on one standard browser (typically the one that the client uses personally).
Once the development task is completed our QA Testing Cycle begins.
The Auro QA Testing Cycle is documented below:
1. The Project Leader initiates the QA Testing Cycle by requesting the QA team to test the website. This initiation is done by providing the requirements document, static screenshots and the link to the website on our testing server.
2. The QA team assigns a QA Lead for each website, responsible for the quality of the website.
3. The QA Lead studies the documents, screenshots and works with the testing website links. After this, the QA Lead plans for a meeting with the Project Team to get a demo of the website and get a full understanding of the system.
4. At this point the QA Lead prepares the QA Testing Specifications Document and gets it approved by the Project Leader.
5. The QA Lead tests the application and presents the results of the testing in Test Results Document to the Project Team. This round of testing is called Build 1.
6. The Project Lead decides whether to accept a finding or reject it. The web development project team fixes the findings that are accepted and all findings rejected by the Project Lead are sent to the Project Manager for approval. The Project Manager decides whether the rejected findings can be ignored, as they are accountable to the client on the quality of the final product.
7. Once the issues are fixed, the web development project team promotes the changes to testing server and submits Build 2 for QA testing.
8. This cycle continues until the QA team has signed off on all the test specifications (except the findings rejected by the PL and approved by the PM).
9. Once the QA team signs off the website on one browser, it is submitted to the client saying it is ready for User Acceptance Testing (UAT). At this point, the QA team continues to test the website on other browsers. This helps us to save time during the parallel testing.
10. Once the QA team signs off on the entire website, the website is officially ‘Out of QA’ and ‘into full UAT’.
This completes the QA Testing Process Cycle as defined at Auro Infotech.