kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 1st, 2009

 

A 'test pass' is another name for 'test run,' 'test cycle,' or 'test iteration'.  In the software industry, it represents a software application that has been delivered to the test team for testing purposes and denotes the span of time and activities that occur from the time a test team receives this application to the time all test execution is finished and results are delivered to stakeholders who make business decisions based on them.

swapnilkude

 Profile Answers by swapnilkude 

• Aug 4th, 2010

 

When the expected results are matches with actual results... it is called as test case pass.

The entry criteria are defined in test plan for inegration level testing... according to it we can say that  the AUT is teatable...

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Aug 25th, 2010

 

Test Passes: When expected result matched with the Actual outcome for the Test Steps, then the status is defined as Passed.

For Integration, each Test Cycle needs a Pass status, that is every Test Run/Test Iteration needs a Passed status for the quality release.

dileepdon

 Profile Answers by dileepdon 

• Jan 2nd, 2011

 

'Test pass' is nothing but a 'test cycle' or 'test iteration' in the Execution phase.

We can also name the 'test pass' as Smoke or Functional or Regression Testing.

mithr17

 Profile Answers by mithr17 

• Nov 2nd, 2011

 

As "kurtz182" rightly mentioned; test passes are test iterations.
QA runs a group of test cases or just one big single test cases to test a feature. This "run" is called test iteration or test run.

Now to the second part of your question. It really depends on the bugs you find and intend to find. You do not have a tailored number for integration testing. It depends on which functionalities or features are tied to the integrations.

The question leads me to believe that you do not know what an 'integration' is. Let's look that!

Example: A database is connected to a web application. This connection is called integration. This is a very basic and simple example. Real-time integration are much more complex.

Now, YOU tell us how many test passes you will need to uncover bugs. QA always test with an impression that application is buggy.