swarna


{ City }
< Country > usa
* Profession * software engneer
User No # 18499
Total Questions Posted # 0
Total Answers Posted # 3

Total Answers Posted for My Questions # 0
Total Views for My Questions # 0

Users Marked my Answers as Correct # 25
Users Marked my Answers as Wrong # 5
Questions / { swarna }
Questions Answers Category Views Company eMail




Answers / { swarna }

Question { 6585 }

What is the difference between integration and system
testing?


Answer

Integration Testing...
two units that have already been tested are
combined into a component and the interface between them is
tested.
System Testing...
In System Testing After complition of
Integration Testing we test the whole application with test
data

Is This Answer Correct ?    2 Yes 1 No

Question { Net Solution, 5726 }

Written Paper at Net Solutions:

1) Difference between Smoke Testing and Sanity Testing.
2) Bug life cycle.
3) Write the steps followed in STLC in your company.
4) Define: 1) BVA (Boundary Value Analysis)
2) ECP (Equivalence Class Partitioning)
5) Write test cases for a login screen with following
fields/buttons:
Username:
Password:
Login (Button)
Cancel (Button)


Answer

Sanity testing:
Sanity Testing is an Initial effort to check whether the
application can be tested further without any interruption.
Basic GUI functionality, connectivity to database are
concentrated here.

Smoke Testing: It covers most crucial functions of the
application.Testing carried out check whether most crucial
functions of the application work fine or not?

Bug life cycle:
A Tester finds a defect and logs it. (But before you
log it, you must try to recreate it for 3 or 4 times so
that you are 100% sure that it is a bug)
The defect is now approved or disapproved by the Test Lead.
(If it is disapproved, then the test lead will come to you
ask for more details and you have explain to him why it is
a bug)
After the Test Lead approves the bug, it is now assigned to
a development Team Lead (or Development Manager). He/she
now assigns that bug to the concerned developer. The
developer now looks into the bug and fixes it. Once the fix
is ready, there will be another build ready to test. The
tester now tests the defect. It the defect is fixed, then
the tester closes the defect, if not then the test will
reopen it and same cycle starts.

Boundary value Analysis:
It has been observer that Program that work correctly for a
set of values. In Equivalence class fail on some special
values these values often lie on boundary of equivalence
class.

1st enter Correct UID/PWD....
Wrong UID/PWD... Error message
Correct Pwd/UID.... Error message etc...

Is This Answer Correct ?    5 Yes 1 No


Question { ACS, 35257 }

types of severity and priority explain some detailed
manner ?


Answer

Hi....,
Severity:
Relative Impact of the Defect i.e How far the
applications is affected by this defect...(Low, Medium,
High, Critical..)

Priority:
Relative Importance of the defect i.e Giving
preference to the Defect...(High, Medium, Low)

Is This Answer Correct ?    18 Yes 3 No