Kumar

• Jul 14th, 2014

If the all requirements are there for a project and they are defined and has the clarity, better to go for any of the traditional Modle ( Waterfall, V- Model, Spiral....etc). If the requirements are ...

ishita13

• Dec 23rd, 2011

Agile methodology has the advantage of accepting the changes at every time in the project till the release time. In this methodology the advantages are : 1. Small releases are made time to time after...

Answer Question  Select Best Answer

Geetanjali

• Sep 4th, 2014

V model is an extension of waterfall model.Its left arm is verification and right arm is validation.verification evaluates the document of the development phase and validation evaluates software appli...

Answer Question  Select Best Answer

What is the difference between Requirement Traceability Matrix and Traceability Matrix?

priya

• Sep 22nd, 2014

Requirement traceability matrix is mapping between the requirements and test cases.that means every req covered with test case or not
Traceability matrix means tracing or mapping between rows and columns

Answer Question  Select Best Answer

sridevi

• Dec 6th, 2014

Retesting is the testing performed on a fixed defect to verify it is working fine or not.

regression testing is the testing performed on the modified application to verify whether the fixed defect is impacting on the other related functionality of the application.

manoj

• Nov 26th, 2014

Whenever there is a change or updation in codings or requirements regression testing is performed it is done to validate that the changes had cause any impact to other modules in a project. Whereas in retesting is to validate the existing testcase after a bug has been fixed.

Answer Question  Select Best Answer

What is co-existence testing? Why do we do it? What would be the passing criteria for a successful co-existence? Any sample application where you feel we require this kind of testing?

Read Best Answer

Editorial / Best Answer

kamal1_batra  

 Profile Answers by kamal1_batra Questions by kamal1_batra

• Member Since Nov-2008 | Feb 11th, 2009

---

Coexistence testing involves the working of application, on different hardware & software configurations. It checks the performance of the application with different combinations of different types of resources.

Compatibility testing checks if the two systems or two different resources are able to exchange the information successfully when an application is implemented or installed. This testing is usually performed when an already existing program is replaced with a new application.

Surendra

• Jan 21st, 2015

Do we have any specific tools to perform the co existance testing or a functional automation tool can automate these activities ?
Please help.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 24th, 2009

Coexistence testing seeks to identify issues when an application works alongside or interacts with other target software on the same machine.  Coexistence testing answers questions such as:1) Wil...

Improve Answer

If a bug is not found in the testing environment and found in production environment, How will you deal with it?

Read Best Answer

Editorial / Best Answer

crazytester  

 Profile Answers by crazytester Questions by crazytester

• Member Since Dec-2009 | Jan 13th, 2010

---

We need to check 1st whether it was within our testing scope or not. If Yes then we have to do a RCA ( Root Cause Analysis). RCA report must be delivered to all the stake holders. 

Devina

• Jun 28th, 2015

If the defect that has occurred is part of test requirement than check for below points: - Try to re-produce same defect on testing environment, to make sure we have not missed it. - Check with the...

Torsten Zelger

• Nov 18th, 2014

Check your regression test suite whether it contains a scenario that could have detected the issue before it went to production. If yes, find out why it was not executed and give it a higher priority ...

Improve Answer

Gaurav.khurana

 Profile Answers by Gaurav.khurana Questions by Gaurav.khurana

• Aug 18th, 2015

Software Testing Life Cycle 1) Requirement phase-->testing Feasibilty , Automation feasibility 2) Planning --> Test plan, test estimation , Resource plan, Risk contingency,Mitigation ,env 3) An...

Abhinav

• Nov 6th, 2014

1. Requirement Gathering
2. Test Planning
3. Test Designing
4. Test Environment Setup
5. Test Execution
6. Test Closure

Answer Question  Select Best Answer

I have a small query in Manual Testing(am working as a Software Test Engineer).I would like to know the definitions of Test Scenarios,Test Conditions with an example.We can Take a Simple example of a Google Page Login or any ATM related scenario...Please help me in finding the solution.Thanks in Advance.

Gaurav.khurana

 Profile Answers by Gaurav.khurana Questions by Gaurav.khurana

• Aug 18th, 2015

Test basis(requirement) --> test conditions (features to be tested)--> test scenarios(different ways of testing --> test cases (inidvidual unit to be tested)

Mayur

• Jun 3rd, 2015

Test scenario is top view of functionality under test in Test scenario what to test the application,test scenarios identifies cover for all test are completed.

Test Cases is define how to test the application, here we are check happy path negative path, alternate.

Answer Question  Select Best Answer

What is the expected result for each of the following test cases?


Rule1 Rule2 Rule3 Rule4
Conditions
----------
Citibank Card Member Yes Yes No No
Type of Room Silver Platinum Silver Platinum

Actions
-------
Offer upgrade To Gold Luxury Yes No No No
Offer upgrade to Silver N/A Yes N/A No

reddy

• Nov 29th, 2015

I think D is correct

triveni

• May 10th, 2012

D

Answer Question  Select Best Answer

shwetali shirke

• Mar 30th, 2016

Yes, closed defect has been tested. As a tester, retesting of defect & regression testing further has to be done.

Bareddy

• Jan 2nd, 2016

According to bug life cycle the bug is closed by tester only.

Answer Question  Select Best Answer

nilesh pingale

• Apr 9th, 2016

Bi-directional testing reduces the testing time. It testing all component they are not tested by Top down and Bottom up integration.

arvind pandey

• Dec 14th, 2006

Hi ,Bidirectional testing means testing the application both with the positive and negative test casescorrect me if i m wrongRegards,Arvind

Answer Question  Select Best Answer

With what type of test is a driver and a stub most closely associated?

Priyank

• Jun 30th, 2016

Driver I used in bottom-up integration approach and stub is used in top-down integration approach.
Driver is a temporary calling Module.
Stub are special purpose programs, not completely implemented and replaced with original module as integration moves downwards in the application structure.

Manmohan Garg

• Jan 11th, 2016

Driver and Stubs are used in integration testing. It is difficult to track defect in an integrated design. So individual module are tested before they are integrated or as soon as a module is develope...

Answer Question  Select Best Answer

Priyank

• Jun 30th, 2016

Verification: 1) The process of evaluating documents of a development phase. 2) Ensures that work product meet their specified requirements. 3) Are we building the product right? Validation: 1) The p...

Archana Sharma

• Sep 3rd, 2015

Validation is to validate that the software which we are building or developing is correct or not.

Verification is the process in which we verifies that the built / developed software is correct or not

Answer Question  Select Best Answer

Which of these is the most important one to fix first, and why?
a. The word "BlackBerry" is misspelled on the startup screen of the application.b. The application always rejects a user's first attempt to launch the application; subsequent attempts are successful.c. The application crashes and brings down the database server when it tries to add a record that contains an uncommon string, "123abc456xyz789".

Read Best Answer

Editorial / Best Answer

vk1978  

 Profile Answers by vk1978 Questions by vk1978

• Member Since Feb-2009 | Mar 25th, 2009

---

Priority will be given based on stage of life cycle,

1) Assume that application is middle stage (I mean to say build is 3rd one and still few more to come) and you are testing the application to accept it (Smoke/sanity Testing) for further testing I would like to give the preference as B, A, C Why I am giving last preference to C is when I am giving uncommon string then the application is getting crash, but as of now we have alternative and that is positive value, so with positive value we can work with the application Next why A is given second preference black berry Its company Name, not a simple title of application

And lastly why I am giving first preference to BI am not able to launch the application in first attempt then it is a major issue, while accepting the build (smoke/sanity testing) if you are not able to launch then definitely we will reject the build.

2) Assume application is completed and ready for use, then also I will give B, A, C Let me tell you in general way, Suppose you are a customer and interested to purchase Blackberry mobile and if it is not launching in first attempt, do you purchase that piece, no one will purchase, and coming second one company Label, Company goodwill is linked to it, and with this mistakes goodwill will be degraded so second preference, and coming to last one we have an alternative and that is we can give positive values with which that particular functionality will work Please correct me if I am wrong.

Priyank

• Jun 30th, 2016

Bug is fixed according to its priority i.e
1) Very High: Immediate fix needed, block further testing.
2) High: Must get fixed before the product is released.
3) Medium: Should fix if time permits.
4) Low: Would like to fix but can be released as it is.

Reddy

• Nov 29th, 2015

I hope that the following ans is helpful... 1) In these scenarios first we have to fix B, why because with out lancing of the application we cant do anything. 2) Secondly we have to fix A. why becau...

Improve Answer

When will you stop testing by ensuring all test cases covered for application?

Krutika Patil

• Apr 25th, 2018

Its depend on many conditions like all requirements are covered, all test plans executed and if the client satisfies with all requirement then we can end testing.

sachin sharmas

• Nov 20th, 2017

It depended on risk of application or software. If application is all bug free and has met with specific requirements than tester can stop testing.

Answer Question  Select Best Answer