Question { Accenture, 17024 }

When to Stop Testing?

Answer

When you meet your Exit Criteria that was in the Test Plan
you wrote before testing began. AND this test plan would
have been approved by key stake holders.

If you cannot meet your Exit Criteria, it is the Key stake
holders who make the decision to stop testing. When this
happens they should be aware that they are now responsible
for the quality of the system that was not tested.

Question { 7767 }

what are the Qualties needed by a softawre tester?

Answer

There are many qualities in a software tester.
One is knowing what quality is. Is quality meeting a
schedule, meeting the budget, having a user friendly ease
of use system, having almost error free code, meeting
requirements, and so on. You need to know this and you
need to put yourself in the position of the customer. if
you were paying for the system, how do you want it to work.
Being a software tester, have you tested the system well
enough for the customer to be happy with it.
A Software tester is someone who tries to break the system.
Because we all know that a user/customer is going to do
something on purpose or by mistake that is not a proper
entry for the functionality.
Also, developers only unit test their code, if they even do
that. A software tester needs to test the system as it is
integrated with other portions of the system. For example;
accouting. You can test the general ledger, payroll,
accounts payable, and accounts receivable separating and
they can all work great. But when you combine all four, are
the proper values stored correctly? Are the account numbers
correct as a whole and per each accounting area (payroll,
AP, AR, GL)
Anyone can perform test cases that have already been
written on paper, A software tester, is the person who
interprets and understands the system requirements, the
code design, attends static reviews, writes the test cases,
sets up the test environment, works with developers, writes
effective defects, tracks defects and brings to a closing,
and provides a current status. A software tester also
needs to write the test plan and get it approved before
testing begins.
There are more qualities/expectations for a software
tester, but these are a few of them to get you started.

Question { Wipro, 20534 }

Who will change the Bug Status as Deffered?

Answer

A deferred defect is a defect that is caused due to a time
constraint and cannot be corrected in the current release
and/or it is due to missing a system requirement and was
never coded or coded correctly. The CCB...Change Control
Board decides if a defect should be deferred. The CCB is
usually comprised of the Project manager, lead/key
developers, and lead/key testers. Sometimes even a key
user or SME (subject matter expert). A developer or tester
alone SHOULD NOT change the status of a defect to deferred.

Question { 9170 }

what is entry and exit creteria for testing ?

Answer

Entrance and Exit criteria is what is important to your
company and the project you are working.
Here is an example of some (not all) requirements you can
write for Entrance and Exit criteria

Entrance Criteria
1. All code for each Phase will be 100% (or near
completion) complete before turning it over to testing.
2. All programming functionality is unit tested by
developers.
3. All test cases have been written per the requirements.
4. Process for defect submission through defect correction
is in place.
4. Test plan has been approved and signed off by key
stakeholders.

Exit Criteria
1. All test cases have been attempted.
2. All Sev 1 HIGH level bugs have been fixed.
3. All Sev 2 MEDIUM level bugs will be fixed or have
management approval to proceed.
4. Exit UAT meeting held and defect results have been
provided and explained.
5. Key stake holders approve testing and agree to proceed
to production.

Question { 9345 }

Why cant a developer test his own software?

Answer

A developer is responsible to unit test their code.
Developers are usually paid more than testers and they are
usually looked upon with more favor by management. With
this in mind, developers don't have time to test. They
bring in the money by writing applications. Also, here is
an example.
a Basic accounting system. You have General Ledger (GL),
Accounts Payable (AP), Accounts Receivable (AR). A
developer may be coding the AR portion or the AP porition.
That portion may work great. But when you combine the GL,
AR, and AP portions, that is when there is a better chance
for defects. Again, a developer does not have the time to
test. if they did, a company would not need to hire a team
of software testers.

And a more simple reason would be, A developer has written
the code, they have unit tested it, they believe it is
correct and therefore to them it doesn't need any more
testing.
When you look at something too much, you tend to have
tunnel vision.

Question { CLG, 81348 }

What is meant by preconditions and postconditions in a Test
Case? Can anyone give an example?

Answer

Pre-condition whatever there is inside or outside of the
system, that will affect how the system will handle the
test. The current state of the system and/or environment
before you run the test case.

Post-condition – anything you expect to happen as a result
of running the test case.
Changes in the state of the system and/or environment as a
result of running the test case.

Question { CLG, 81348 }

What is meant by preconditions and postconditions in a Test
Case? Can anyone give an example?

Answer

Preconditions – Anything the solution can assume to be true when the use case begins.
Post Conditions – Anything that must be true when the use case is complete.
there are 4 parts to a test case
Pre Conditions
Input
Output
Post Conditions

Question { CSC, 14880 }

What are the steps, procedures, objectives to write test
cases.

Answer

The first step in writing a test case is reading and
understanding the requirements. there should be a minimum
of one test case per requirement, though you will have more
test cases per requirement.
Most test cases are negative test cases. What happens when
an entry is made that should not have been made.
procedure: you write the steps to perform the test case.
You already have expected results. After the test case is
performed, you enter a P for pass, F for fail, B for
blocked. and other comments. You also have a column for the
requirement you tested.
The obectives of a test case is to make sure the
requirement is met and the functionality works as
designed/requested. You also make sure that incorrect
entries (negative test cases) are tested and that valid
error messages (when needed) are displayed.
Don't forget to document your testing cases and record
important information such as the build number, date, and
person performing the test.
These are just a few of many steps and procedures needed to
write effective test cases.

Question { Cap Gemini, 4680 }

How will you get the Data requirement for your testing?

Answer

Any testing that you perform should have requirements. If
someone asked you to test functionality on a system, they
or the user need to tell you what they expect and what the
outcome should be. If there isn't a formal system
requirement, then from the information you gather, you
write the requirement for the testing you are asked to
perform.
If you are asking about DATA, be it numeric or such as
name, address, city, state, zip code data requirements.
This information also comes from the person requesting the
testing.
NOTE:
If you don't know what to do, you can't know how to do it.

In other words, how can you test something that you don't
have the correct information. How will you know if the test
case passed or failed, or if your test case is even valid?