Software police concepts

Fault based testing

Fault-based testing is a very effective technique for
determining the validity of test suites.
2.
By introducing faults into code, either by hand-seeding
or using an automated mutant generator, then running a
set of tests on the mutants, one can determine if the
test set is sufficient for the program or not.


RTVM

ITS REQUIREMENT TRACEABILITY MATRICS OR REQUIREMENT TRACEABILITY VERIFICATION MATRICS IT HELPS IN VERIFYING WEATHER THE REQUIREMENTS AND THE TEST CASES ARE MATCHING AND ARE PLANNED WELL OR NOT SIMPLE TO SAY IT IS MATCHING THE TESTCASES TO THE REQUIREMENTS

Is Th

Continue lendo

Test scenario - Very helpful for freshers.

1.They showed me a Web page containing 3 text boxes labeled as
Name, D.O.B & Blood Group.It also have 3 Buttons as OK,
CANCEL,Reset. They told me that 
1) when you click on OK it'll route you to the next page and
save the data in the database.

2) When you click on CANCEL it'll route you to the previous
page.

3) When you click on Reset it'll clears all the entries made
by you.

Now they asked me to write Test cases to test the
functionality of that web page & asked me to write 1
critical test case after which they will give final go ahead
to test the rest of the application...

Answer

1.  Enter valid Name, DOB, and Blood group

     Click on OK

     Expected: Page should navigate to Next page and updated data should display in database



2. Enter invalid data in one of the fields

    Click on ok

    Expected: Error msg should be displayed and no data  should update in database



3. After entering the valid data, update the data in the 

database (Critical)

Expected: based on the changes, the respective updated 

information should be displayed



4. Enter valid data

Click on cancel

Expected: It should navigate to previous page and no data 

should update in database



5. Enter valid data

Click on Reset

Expected: It should clear all the entries made by you and 

no data should update in database



6. After clicking on Reset click on Ok(Critical)

Expected: Error msg should be displayed and no data should 

update in database 

2.what is mean by test preparation? and explain it?  

Test Preparation is checklist of the activities that to be done before starting testing of application.

Requirement Analysis.

Test Planning.

Test Case Development.

Test Environment Setup.

Test Execution.

Test Cycle Closure .

3.which phase is most important in STLC phases? and why ?

Requirement Analysis and Test Planning are the most prominent stages of STLC. If requirements are not analyzed 
correctly,plan will make accordingly and test cases will also developed 
incorrect. 

4.What can be done if requirements are changing continuously?

If client requirements are changing 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. 
             
           

Continue lendo

3:3

1.Database tetsing???

The method you want to test executes a rather large JOIN operation and uses the data to calculate some important results. Your business logic performs a mix of SELECT, INSERT, UPDATE and DELETE statements. You need to setup test data in (possibly much) more than two tables to get reasonable initial data for the methods you want to test. The DbUnit extension considerably simplifies the setup of a database for testing purposes and allows to verify the contents of a database after performing a series of operations. Sample test case for database testing: The test case for the above requirement is mentioned below: Test_Case_Id:1 Test_Case_Name:Check the unique identity of Student. Description:Test case to check the unique identity of Student. Prerequisite: 1.Database should be present 2.Student records should be present in student table. Input Data:1.Open your database(SQl,oracle or any which you are using) 2.Open its command prompt editor. 3.Select the proper database 4.Enter the query as:"Select * from Student_Details" 5.Run the query. Expected Result: The all unique student records will be displayed. Validation:Student is should be unique.

2.What is Facets testing ??

Facet means small small aspect or attributes.All the filter criteria options can come under
facets,testing of these size,name,contains is called as facet testing.

3.How we Check Perfomance testing In Manual?

If there is a back end database to the Web app you can use the database Performance analyser

tool to evaluate the same.General web apps are performance tested in terms of the time taken 

to load a page. This is manually timed using the systems clock.

For client server apps : The performance c/s apps is manually checked again using the systems

clock to validate the server response to a client request.The above tests are done only for fine 

tuning purpose of the applications.If the performance under load is to be tested a use of tool 
is essential.

Continue lendo

Three Three

1.Differences between smoke,sanity,regression and Retesting???

SMOKE TESTING: TESTING DONE TO CHECK WHETHER THE BUILT  RELEASED IS STABLE ENOUGH FOR FURTHUR TESTING OR NOT  SO THIS IS THE FIRST IN OUR LIST.

RETESTING: ONCE THE BUG IS FIXED THEY RETEST THE FEATURE TO VERIFY THE BUG IS STILL PRESENT OR NOT.SO THIS WILL COME 2ND IN LINE.

REGRESSION TESTING:TO VERIFY THE BUG FIX DINT EFFECT
ALREADY WORKING FEATURES. SO THIS ID 3RD IN THE LINE

SANITY:IN MOST COMPANIES SMOKE/SANITY USE AS ONE BUT

SANITY TESTING IS TO VERIFY THE APPLICATION WHICH THEY R
GONNA RELESE SOON IS  STABLE WHITOUT ANY CRITICAL BUG.

DIFF BETWWEN SMOKE AND SANITY IS THE TIME THEY R TESTED.

2.Entry and Exit criteria?
Entry Criteria:
1 All code of application, unit tested.
2 Test plan, test cases reviewed and approved.
3 QA/Tester get significant knowledge of application.
4 Test environment/test ware get prepared.
5 After getting application build.
Exit Criteria:
Deadlines (release deadlines, testing deadlines, etc.)
Test cases completed with certain percentage passed
Test budget depleted
Coverage of code/functionality/requirements reaches a
specified point
Bug rate falls below a certain level
Beta or alpha testing period ends.



3.Testing process.....
Project finalized
Requirement analysis
Formal meeting with team members
Writing test cases
Review of test cases with developers
Test environment setup
Executing testcases
Bug Anatomy
Bug reporting
Regression testing
Retesting
Sanity testing
Test closure report
sign off.

 

Continue lendo

3 : 3

1.What is Risk and mitigation plan?????
Project Manager is responsible for preparing Risk Mitigation strategy. However, he might would like to take inputs from the project team leads/members, BAs, QA, SQA
and IT infrastructure support teams to come up with an effective mitigation plan.


Mitigation has to do with devising one or more approaches to control, avoid, minimize, or otherwise mitigate the risk. Mitigation approaches may reduce the probability or the impact. It is more of a PROACTIVE initiative even before the risk becomes a problem.


The objective of a mitigation should be to ensure a risk identified doesn't occur or the least reduce it's probability of occurence.


Contingency plan on the other hand has to do with what if you are hit by the problem for the risks you could not mitigate. (This is in contrast a REACTIVE mode).

2.When to stop testing?????
When to stop testing" is one of the most difficult questions to a test engineer. The following are few of the common Test Stop criteria:


- All the high priority bugs are fixed.
- The rate at which bugs are found is too small.
- The testing budget is exhausted.
- The project duration is completed.
- The risk in the project is under acceptable limit.


3.What is bug reproduce?????
You can reproduce a Bug during Regression testing.There is nothing like a 'Reproduce' state in Bug life cycle as the Bug life cycle starts at finding a bug and end when the defect is retested successfully to close/end bug life cycle.Usually bugs can be found during regression testing which would have caused due to a fix in some other functionality.

 

Continue lendo