Is there any standard procedure to test the application as a whole? Or How can I test complete application right from the requirement gathering?
Here are the broad steps to test the application :These are the standard SQA peocesses to be followed in any application testing.
- Marketing Requirements
Review of the Objectives set for the Last Released Build
Objectives remaining to be completed are carried forward for the next release.
- Branching for the development cycle
- Objectives settings for the Major and customized releases
Target Date planned for the Releases and decision on the entire Project schedule that is required to achieve these target dates.
- A Detailed Project Plan and the release of design Specifications
This includes the decision on Design Specifications (Productwise), review of the design specs and development schedule. This involves QA during the phase of review.
- QA – Develop Test Plan based on Design Specifications
Test Plan : This is a top-level document that talks about how the product is going to be tested
This includes Objectives, Methodology adopted while testing, Features to be tested and not to be tested, risk criteria, testing schedule, cross-platform support and the resource allocation for testing.
Feature Test Plan : This document talks about how the testing is going to be carried out for each type of testing.
- QA – Functional Test Specifications
This document includes technical details (Software requirements) required prior to the testing. It is important from the tester’s point of view to understand and plan the technical resources prior to the testing.
Application Development : Considering the product features, tester has to make ready his/her own test suit.
- QA – Writing of Test Cases (CM)
- Smoke (BVT) test cases
- Sanity Test cases
- Regression Test Cases
- Extended Test Cases
- Negative Test Cases
- Development – Goes on Module by Module.
- Installers Binding and Building
- Installers are built around the individual product.
- Release Engg is responsible for releasing the Builds.
- Release Engg collects fresh/developed code from the developer’s initially/module wise.
- Installers have to take care of jar files updating, registry entries, and additional software installations.
- Build Procedure :
- A build includes Installers of the available products – multiple platforms.
- For each build one or 2 CDs are made/build the same are pushed to Pune/Chennai based on the priority.
- Each product build are received in the form of zip files under http://pun-qaftp/ftproot/QA-Builds ( Pune-Specific). The procedure goes along for Chennai. San Jose QA picks up builds from Nexus ( Build Specific Server )
- The same zip files need to be unzipped to get the desired installer and the same is put at Pun_fps1/QA/Builds folder. ( Pune-Specific)
- QA – Testing :
- Smoke Test (BVT) to check basic features of the product.
- Smoke Test results has to be posted on http://Chaquita which is an official site for posting Smoke
- Test results and to share the basic testing information.
- Prepare Smoke Test procedure.
- QA – Extensive testing :
- Testing of new features
- Document review
- Cross-platform testing
- Stress testing and memory leakage testing.
- QA- Bug Reporting :
- Use of Trackweb’s “Soffront” as the Bug Tracking tool.
- Further FET (Fixed Effectiveness testing) of the filed bugs.
- Exception study and verification.
- Development – Code freeze :
No more new features are added at this point.
- QA – Testing :
Candidate Builds and regression testing.
- QA- Media Verification :
CDs are cut for the released products and the product is installed using those CDs and it takes place in San Jose.
- Decision to release the product :
A review meeting to analyze the performance of the product, which is set, and the same is compared with the objectives set.
- Post-release Scenario :
One branch is kept for the post release modification and hence the product testing.
Post release review meeting to decide upon the objectives for the next release.
24 comments ↓
hi can u tell me how to determine? the number of test cases to be written.
@Sachin,
I think I can help you. For every given application you must write 3 test cases which always finds as many important problems, quickly and provides quality related information to help the management take decisions.
If you are on a project where your manager is not aware of what testing is all about, you might want to write thousands of them to impress him, execute a few, find a few bugs ( that dance before you ) and map it to a test case.
If you are a bit lucky to get a manager who is aware that, the number of test cases is not important but information about the quality, you live longer as a tester.
If that’s too technical, here is something that you might like to answer:
You buy a mobile phone and you find that it disconnects a call after ever minute and you are annoyed and call up the company support number to report this problem and you get a reply: “Our testers have already 1983498348 test cases and we have no time to execute the ones that are already existing and we can’t take buy your idea” , would you or your manager enjoy that moment and say, “Wow! you have 1983498348 test cases for this phone”?
Hai i am saravanan from coimbatore..i am working as a software test engineer for last 1 year..i attended one interview in that they asked me how many test case u can develop for one day…i dont to answer that question…tell me what can i say..
Hi Saravanan,
Let me tell you first that Test case is not measured on the basis of quantity but on quality.
You should give preference to write the quality test cases not the number. I am using word ‘quality’ means in those test cases most of the application get covered. Then you can think of writing ‘enhancement to product’ test cases.
And also important thing as mentioned by Pradeep in above response, ‘there is no use of writing million test cases if you are not able to execute them’!
So answer to your question is simple, “I will try to write the test cases that will cover all the modules and the product”.
hi
what are hte documents we have to maintain form the (as a tester) stating the testing to end of testing
@ Balu - A good question from QA perspective. Maintaining documents depends on your role in project. As you are talking about ‘tester’, Here is the list of documnets to be maintained from project start to end:
1) Test plan
2) Acceptance criteria
3) Test design specification - specifies how a feature or group of features will be tested
4) Test case specification
5) Test procedure
6) Test script: all about getting started, description of each test
7) Test summary and Test log
Please tell me different test metrics
Some times there is no sign off from the client of dociuments and writing the test cases on the same. How it is possible to update the test cases everytime if changes are going continue in SRS?
@ sricharan - Test metrics are the measures of the quality of the product and used to take action immediately on the quality affecting areas.
Various Test metrics includes:
Quality of written code
Number of defects and Test effectiveness
Testing time
Development time
Quality of product determined from defects
Testing cost in terms of resources and money
Cost per defect
Development cost
@ Manoj - The ideal solution is Freeze the requirements.
But this is not possible as many times client requirements goes on changing due to some circumstances an dour product must satisfy those requirements. Speaking specifically about the test cases we can maintain a traceability matrix which will show the dependent modules or the functionality dependency matrix which can be used to modify the test cases only for the affected modules.
Sachin,
It depends on your application and your requirements. The most dependable outcome will be to come up with a path that will show the real outcome of your goals. They you can proceed to have a good solid understanding of how many test cases you need. Please go to this testing forum site www.softestclub.com
It has some other formulars that you can use also. Thanks
plz tell me how you are going to test in protocol testing. like sip and voip . what is procedure to follow give some ex.
How to test an application using QTP.
Hi
I would like to know what would be the appropriate answer for the follwing interview question
“What would be your test approach for testing an “Air conditioner” or “Cofee machine” or “Mobile Handset” etc.
Send me some of the datadriven automation framework, if possible send them with script
thanx n regards,
venkatesh
hi,
what are all the contents of test execution report.
Hi Sandeep,
This is a sure shot question in any testing interview.
The interviewer may even ask you to test a tennis ball, a pen or anything thats on his table.
I have an answer for this….
To test anything, we can consider three points:
1. Look n Feel
2. Functionality and
3. performance.
look n feel is how does the object look, its color shape ,evrything counts.
When it comes to functionality, is that object performing its basic functionality r not, is what we test
(for ex: basic functionality of a pen is to write whereas a ball’s functionality is to bounce back when it hits the ground)
Finally performance… this is all about how that object performs in long run. that is if its keep on working, how does the object perform.
I hope this is how we can give an answer for such kinda questions.. coz, even i was asked the same question in an interview and the interviewer seems to be pleased with that answer and thats the reason, I am now a software test engineer..
Anyways, all the best buddy…
what is QA responsibilities ………
they are doing
Quality assurance process
Hi,
My name is Thao. I’m come from Vietnam.
I alway surf this website, but my English is not very good.
Uhm, can you explain what’s “Smoke Testing mean???
Please
Hi Thao, You may want to check out the latest post on smoke and sanity testing to clear your doubts:
http://www.softwaretestinghelp.....ifference/
Thanks you so much,
I will check it
Hi,
Can anybody please guide me to answer how we can give Test Estimate. (If My manager comes to me and ask for the estimate for the work which is assigned to me and I am comfortable testing that)
hi……
Hi Viji,
Iam working for Software company for last two Years.
Problem facing while selecting automation tool (Ex. QTP, SilTest, WinRunner) for application testing and also after selection what problem we generally face while doing automation.
Leave a Comment