W:
Team was of 10 people and a lead.
Here, I found that the QA was very process-oriented. The reason for being so was that, there were QA Audits done periodically.
Ambiguity reviews: It was something I did for the first time. Works like this:
As soon as you get the FSDs, you should read it thoroughly, and write down anything that is not clear, ambiguous, confusing, stops you from writing test cases. Send this document to the BA for clarification. BA is supposed to write the resolution for each ambiguity and send it back to you. This process could get iterative. Once you make sure you don't have any more ambiguities, upload the document to a shared location and publish it.
Create one ambiguity document per FSD. As with any other project doc, write the date, history and other tracking information in it.
NOTE: The resolutions suggested by the BA would be incorporated in the FSDs, eventually. Until then, you are supposed to use Ambiguity review doc as an addendum to the FSD.
N:
This was really a good company to work for, and I earned a lot of experience here.
We were following Agile Development methodology.
I was responsible for functional QA of the product. The product was an enterprise application for a Service Catalog management. It allows the IT department to design and advertise its service catalog. Allows the users to order a service and create a service request, and also allows the fulfilment of the request. It involves a lot of Workflow testing. We extensively used HP quality Center for writing test cases, running test labs and logging/tracking bugs.
Note about QC: If we use QC for Requirements as well as test case development, it becomes easier to generate traceability matrix (which maps the requirements to the testcases). This way we know immediately if a particular requirement is covered by enough test cases (or not).
I wrote test plans for different features of the product. Also, I developed functional and integration test cases for those features.
I identified integration scenarios between 2 (or more) features.
I was responsible for maintaining regression test suite across multiple releases and interim (bug-fix) releases. For a bug-fix release, it is required to identify which regression tests are to be run. This depends on the areas in which bug fixes have happened. Intention is to make sure the bug fix hasn’t broken any existing functionality.
We had peer testcase reviews, when we used to review cases written by peers.
Test data creation: Two approaches: We used to export data in xml format and import whenever required.
I had written automated scripts in QTP, which would actually go and create data.
Our automation team was in India. I worked with them to get tests automated: identified the tests to be automated, re-wrote them in more details (with screen shots etc), and had them write the automation scripts. Verified locally that the scripts are doing what they are supposed to do.
Cross-browser testing: We tested the application on IE6, IE7, FireFox and Safari.
I also did web services testing using soapUI.
A note about web services testing:
WSDL: Web Services Description Language
SOAP: Simple Object Access Protocol
Web Service testing:
A web service will have a WSDL associated with it.
In order to create test cases for a web service testing in SoapUI:
- Create a new project
- Add corresponding WSDL using a URL (or a file)
- Create default requests for each operation
- Select an operation and open the default request
- Supply input parameters by replacing ‘?’ .
- Post the request by clicking on green arrow.
- A response will be displayed in the right-hand panel.
A:
I was the only QA person in the company and was leading an offshore team of 8 QA testers.
The company had 4 different products, all in the Network Performance Monitoring domain (Web, IPSP, TCPIP, eRoute, cTrace). I was responsible for defining QA policies and procedures for all the 4 products.
This included:
- QA Plan at the company level.
- Test plans for each product.
- Release schedule for all products
- Coordination with Beta customers for Beta testing.
- Being administrator for the bug tracking tool (Test Track Pro).
Test Coordination: I got the test cases written from the offshore QA team and had them execute them. Also administered Used TestComplete in order to automate some of the tests.
