Question { TCS, 8633 }

why need testing ????

Answer

Testing is required

1. To check whether the software or system is bug free or
not (Though we can not gurantee that the developed system
is 100% bug free)
2. Top check whether there is any deviation in the system
or whether the developed products meets customer
requirements or not.
3. To check the performance of the software, relaibility,
compatibility, portability.
4. Fit for use

Question { 8886 }

how to write the test case for 1 to 12 months in equivalence
partitioning?

Answer

In equivalence partioning, equivalence classes are created.

In this example the range is from 1 - 12.

So we can write a single test case with any value between 1
to 12. If it gets passed then the application will work
with any of the values between 1 to 12.

If we want to perform boundry value analysis, then the
inputs that are required are

min value -> 1
min - 1 -> 0
min + 1 -> 2
max value -> 12
max - 1 -> 11
max + 1 -> 13

So total 6 test cases are required.

Question { 5978 }

Can any one please tell me what is the use of negative test
cases when we are giving the invalid input in test data

Answer

Negative test cases are written so as to check how the
system/software behaves when invalid input is entered.

System should display the appropiate error message as per
the validations that are configured. It should not get
crash. It should not get hang.

Question { WinSoft, 4241 }

What are the stages of the Bug?? What is the exact life cycle of the bug??

Answer

Bug life cycle

1. When a new bug is found, it is assigned status as NEW
and is assigned to developer.

2. The project manager checks whether the bug is valid or
not. Suppose for billing sysytem the valid password is dang
& the tester is testing the functionality with some other
password wich causes login failure, en the manager will
assign the status as REJECTED & assign it back to tester.

3. If defect is valid then it is checked whether it is in
scope or not. If not, then the defect is assigned status as
POSTPONED.
4. Then it is checked whether same defect was raised
earlier or not. If yes, then the defect is assigned status
as DUPLICATE.
5. If no, then the defect is assigned to developer with
status IN PROGRESS.
6. Once the defect is fixed, it's status changes to fixed &
assigned to tester.
7. then the tester will retest & if it is fixed then assign
status as closed.
8. If not, then it is reopened.

Question { 5166 }

How System testing is different from the Functional testing??

Answer

Testing the behaviour of system / software as defined in
software requirement specification is called system testing.

It checks for functional and non functional requirements of
the software.

System testing is performed after integration testing.

Before accepting the system testing, tester should perform
smoke testing so as to check whether basic functionalities
are working fine or not.

Question { Oracle, 18642 }

What can be done if requirements are changing continuously?

Answer

If client requirements are chaging continuously, then below
changes are expected.

1. Change in design document or new design document HLD &
LLD
2. Change in test case scenarios
3. Change in test cases
4. Developer needs to write the code as per the change.
5. Tester needs to write new test cases
6. Tester needs to test the change.
7. In agile, work done in iteration can be affected.
8. Involves more cost.