Gaurav Khurana

• Feb 25th, 2015

A product is never defect free. When you met the exit criteria, you can assure that there should not be any defects left in the product if rigrous testing is done. Testing can never certify that there are no more bugs left in the applicationt

Sneha

• Nov 12th, 2014

The product is defect free when it meets the requirements given by the user and also when there are relatively low priority bug.

Answer Question  Select Best Answer

When the application is ready for testing but there no time as customer needs the application very soon, what is the solution for testing

siva

• Jul 7th, 2015

For every Project All test cases are prioritized into P1, P2, P3....based on differnet factors like KBFs(Key business Flows), Complex areas, High Risk Areas, Frequent defect causing areas etc...so whe...

Sachin Kumar

• Feb 2nd, 2015

Once Application is Ready But customer needs the application soon .... then we need to go for Ad-hoc Testing...

Answer Question  Select Best Answer

SACHIN NADIG N.K

• Aug 20th, 2015

No. Because developer has a confident that his build work
He has a over confident on his product
He cannot see the product crash

Answer Question  Select Best Answer

Anil Nakhate

• Sep 7th, 2015

As a tester, First we need to perform basic functionality of application like URL, Home page is working or not i.e Smoke Testing.

After performing smoke testing then we need to perform sanity testing i.e need to one of function in depth or in detail .

sonal shrivastava

• Sep 3rd, 2015

First we perform smoke testing to check the build is stable or not we check the basic functionality.

Answer Question  Select Best Answer

Adamshafi

• Oct 6th, 2015

First step is to go through the requirement doc and even if tester is not clear then should contact the PM(Product Managre/BA).
If PM says its deviation from the expected behavior then directly raise the bug without discussing it with developer.
NO NEED TO DISCUSS the behavior with developer.

Palak

• Feb 16th, 2015

My first step will be to reproduce the defect and show it to the developer with each and every step clearly as per the requirement. If there is still an disagreement and I am sure about the requiremen...

Answer Question  Select Best Answer

If any bug found by the tester and send it to developer but developer saying its not bug and its process or functionality but tester ( on behalf of client ) is saying that its a bug.

Then what will happen with that BUG number. This all bug report should be send to client.

But this bug should be what ??? How the tester / developer / project manager / test manager will handled.

Vrushali Tupe

• May 3rd, 2016

1) If bug have high severity then as a tester we have to convince to a developer if developer not accepting that high severity bug then it should be report to project manager. 2) Check whether bug is...

Bhavani

• Sep 24th, 2012

In the defect report, the tester should specify the details such as parameters,environment,screenshots,..etc to the developer to reproduce the scenario. If the Developer cannot reproduce the issue,c...

Answer Question  Select Best Answer

mamta sharma

• Aug 30th, 2016

Walk Through: A meeting with the other members
Inspection: Controling and Programming
Peer Review: Rework and Release

Marianthui

• Jun 24th, 2016

Walk Through: A meeting with the other members
Inspection: Control and Programming
Peer Review: Rework and Release

Answer Question  Select Best Answer

Is it mandatory that a good tester must be a good leader? Explain

suvarnaTEC

• Jul 21st, 2017

Bug: Small deviation between expected and observed output

Error: Compile time it can occur that is called error

swapna

• Jul 17th, 2017

Error: These are occurred at run time like missing parenthesis({}), statement missing(;)etc.

Bug: It means small deviation between actual and expected output. Like suppose we want sum a+b instead of using a+b we are using a-b

Answer Question  Select Best Answer

Give some reasons

shivaraj kumar

• Aug 24th, 2017

Before a build is released for testing team, developer will perform basic validation testing and once the build is released 1st most basic step - Sanity test will done by a tester. Once a sanity test has been passed then only the build will move further for functional tests etc.,

jag37

 Profile Answers by jag37 Questions by jag37

• Jul 2nd, 2014

Hi Surbhi,

Sanity testing should be done by testers and developers will not involve, because sanity test basically have more number of test cases where dev will test only basic functionality of product before send to testers

Answer Question  Select Best Answer

What will be your approach for testing an application when not much documentation is followed as well as time is less for testing

Sachin Sbarma

• Nov 20th, 2017

Testing with no documentation is called "AD-HOC" Testing and it is used to testing the application or software without any documentation and test cases.

devi puri

• Jan 5th, 2017

What your opinion about this situation is exacerbated by the increasing popularity of Agile methodologies?

Answer Question  Select Best Answer

What are the testing types and techniques?

Sachin Sharma

• Nov 20th, 2017

Testing types:- 1.On Basis of code:- White Box testing and Black Box testing. 2.On basis of function:- Functional testing and Non- functional testing 3.On basis of Tools:- Manual and Automated test...

shivaraj

• Aug 24th, 2017

Basically 3 Types: 1.Black box testing (Done by tester) 2.Whitebox testing (Done by a program knowledge person) 3.Graybox testing (Combination of both) Testing Techniques: Sanity testing Functional ...

Answer Question  Select Best Answer

Sumedh

• Jun 19th, 2021

Error is a mistake find in the program, a tester finds the error called as defect & and this type is accepted by the developer is called a bug.

suvarnaTEC

• Jul 17th, 2017

Bug:
Small deviation between actual and expected output.
It can rectify testers.

Error:
It can occur compile time.
It can rectify programmers

Answer Question  Select Best Answer