-
Test cases for Mandatory Fields
A Page/Form has 4 Mandatory fields to be entered before you Submit.How many no. of test cases are required to verify this?And What are they?
-
Testing Production Issues
Say you are working on a release and productions issues occur that are in need of a fast fix, test and deployment back into the production environment.How would you handle that
ashishks
- Sep 9th, 2009
Once you find any defect on production, log a defect immediately having "HIGH" priority.Once developer fixes the defect test same issue and do sanity/regression testing depend on the time available.
mathan_vel
- Apr 2nd, 2009
I note down the issue in the Bug Tracking System and mentioned the Severity & Priority level for the arised bug and make note on the causes happened(might be a Show Stopper). i informed about this bug immediately to my TL and request the Dev to fix the bug as early.
-
Intergration testing
How you will write test cases for integration testing? Explain me with an example
sharads
- Dec 7th, 2009
Before we begin Integration Testing it is important that all the components have been successfully unit tested.Integration Testing Steps: Integration Testing typically involves the following Steps: ...
Himanshu Man
- Oct 8th, 2008
Testing of 2 or more than 2 modules of application/applications is integration testing. It involves validation of data flow via xml or any other technology in between modules.
-
New Bug and Open Bug
What is the difference between New and Open bug? Who is responsible for changing the phase of bug from New to Open?
krishnalatha
- Jun 23rd, 2010
When a tester creates or enters a new bug, he can assign the bug to 2 different people, one is directly to the concerned Developer, or TL or PM. When we directly assign to the developer, the deve...
kurtz182
- Dec 17th, 2009
A new bug is one that has not been reviewed and assigned. An open bug is one that has undergone a review process and a Project Manager has assigned it to someone (ex: development staff, business analyst, etc.) for further research.
-
difference between alpha Testing and beta testing
Read Best Answer
Editorial / Best Answer
sprdpr- Member Since Jul-2008 | Jul 17th, 2008
If the project or product is developed for multiple customers, acceptance testing will be conducted in two phases called Alpha and Beta testing.
Alpha: Acceptance testing conducted by the customer in the developed environment.
This testing will be conducted to identify all the potential issues before releasing it(product/project) to the customers.
Beta: Acceptance testing conducted by the multiple customers in the customer environment.
Alpha and beta always prefered for the products.
Correct me if im wrong.Ezilarasn
- Oct 25th, 2017
Not correct exactly Alpha testing is final Testing befor the S/W is realeased to the general public. It has two phase First Phase Alpha Testing: S/W is tested by developers. They use either debug...
Rajkumar
- Jul 17th, 2014
Alpha Testing Beta Testing (Field Testing) 1. It is always performed by the developers at the software development site. 1. It is always performed by the customers at their own site. 2. S...
-
Bug status
What more status can you give to a test case other than pass, fail, not run & blocked?
-
missing important bug
If i miss a important bug and i realise it very late then what will i do?
kishore11m
- Aug 11th, 2010
First check whether the bug existed in your scope or not, if it is in your scope, check whether you have covered the senario in testcase document, if not, prepare a Root Cause Analysis Report and send to the team lead.
DattaDeshmukh
- Apr 9th, 2010
Every bug you founf is important. If you found it at the end of release cycle then also inform it/log it. Let the BA decide what to do with it. If it is critical/major then it should be fixed. If it is normal/minor/corner case then can be deffered to next relase.ThanksDatta Deshmukh
-
Integration testing
Who is resposible for integration testing?
Read Best Answer
Editorial / Best Answer
surendra_kumar- Member Since Nov-2006 | Jun 11th, 2008
it is not just the developer OR the Tester is responsible for integration testing, Both of them are equally responsible according to their responsibilities. The developer who writes the code is responsible for performing the integration of modules w.r.t. code ( should be understood as part White Box Testing ) Then after checking the modules for their integration it will be passed on to the Q.A. team, Here it will be the responsibility of the Q.A. team to check the integration b/w the modules according to the requirement specifications.
manii17k
- Oct 13th, 2010
Don't worry about integration testing but u need to have idea about tht basically integration testing is done by white box test engg (developers )but as a black box test engg u need to have that idea .
mathan_vel
- Oct 12th, 2010
Integration Tester(Integration QA Analyst) is responsible for the Integration. Its up to the role of the tester. But in our concern for Integration QA Analyst is the responsible person.
-
what are test bugs?
mattd1
- Feb 28th, 2010
Test bugs could mean anything. It depends on the context.It could mean -1. Bugs identified by test team2. Verification of fixed bugs.
kurtz182
- Dec 9th, 2009
In my organization, "test bugs" are those discovered by the in-house test team in the test environment whereas "production bugs" are those found by the general public in the production environment.
-
Did u ever have to deal with someone who doesn't believe in testing? What did u do?
kanchanG
- Nov 19th, 2009
We can even give example of Vehicles like Car, if new Car has been launched in the market then it is supposed to be test first, before Customer using it , parts like breaks, tyre, horn headlight are w...
Sushma Mosali
- Aug 27th, 2008
hi,Initially, Depending upon on individual interests people choose their fields, But if they do not believe in testing then i would ask them to go through the book "Lessons Learned in S/W Testing...
