Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...


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)

Answers were Sorted based on User's Feedback



Written Paper at Net Solutions: 1) Difference between Smoke Testing and Sanity Testing. 2) Bug l..

Answer / vidya

Diff. bet Smoke and Sanity testing:
Smoke Testing: Whenever a new build comes to test the high
level of functionality in the application and ensure that
the build is ready for detail testing.

Sanity testing: In this type of testing the behavior of the
system are test. Test whether the system is working
smotthly whiout any unexpected error.

Bug Life Cycle:
Whenever a defect found we marked the test as "New". Then
TL or onsite coordinator verifies the bug and mrked the
status as "Open". Then it goes to developers plate. At
developer end Developer head marked the status
as "Development Assign". When it assgin to a particular
developer marked the status as "Dev Started". Developer
worked on the bug and categorised this in 3 types:
Fixed - For fixing the valid bug.
Dev Rejected - Invalid bug
Deffered - Functionality included in the next release.
After that it again comes to the tester's end. Then tester
again worked on the bug and if it is fixed marked the
status as "Closed". If it is not fixed marked the status
as "Reopen".

Steps followed in STLC:
1. Understand the requirements.
2. Creation of Test Plan
3. Creation of Test Cases.
4. Execution of test cases.
5. Defect reporting
6. Resolution of defect
7. Regression

Define BVA:
In this for a given range we are most concern of the
boundries. 3 valid test cases and two invalid test cases.
For. e.g to test BVA for 1 to 100 then possible test cases
are:
1. valid: 1,2,99,100, In between the range
2. Invalid: 0, 101

ECP:
BVA is done in ECP. The range is devided in the paritions
and for each partition we chck the boundries.

Test Cases for login:
1. Username and Password with valid data.
2. Keeping one or both fields blank.
3. Invalid data for both the field.
4. Login to the application with valid data.
5. Cancel buttton with and without entering the value.

Is This Answer Correct ?    7 Yes 2 No

Written Paper at Net Solutions: 1) Difference between Smoke Testing and Sanity Testing. 2) Bug l..

Answer / swarna

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

Post New Answer

More Manual Testing Interview Questions

how recovery manager works in winrunner

0 Answers   QA,


any one please send me any test case examples with tabular columns in manual testing

0 Answers   Satyam,


what is testing?

5 Answers   Naukri.com, RealTech, TCS, Value Labs,


Describe your experiences with code analyzers.

0 Answers   HCL,


How to check the Performance of the website during manual testing.(guys its very urgent plz)

4 Answers  


what type of document we prepare while testing?

1 Answers  


1. what is severity and priority and who will decide what .?

8 Answers   Winspire Solutions,


What is bug, deffect, issue, error?

0 Answers  


Difference btween the QA and QC?

6 Answers  


say me any problem u faced in the project after delivering to client?

2 Answers   Mantra Group,


What is difference between individual test team testing and self testing by developer? give pros n cons.

2 Answers   Persistent,


Can you explain regression testing and confirmation testing?

0 Answers  


Categories