MANUAL TESTING VERY IMP QUESTIONS

                                                       INTERVIEW QUESTION

Manual Testing

Traceability Matrix?

Ans: Traceability matrix nothing but it contains table of linking information. WHICH is used for tracing back for the reference whenever there is a questionable situation

Test Case-definition and prepared by whom?

Ans: it case is nothing but it is an idea of test engineer based on the customer requirements. Prepared by test engineer

Use Case-definition and prepared by whom?

Ans: use case is nothing but it will describe the all the functionalities in the application. Prepared by business analyst

Test Plan- definition and prepared by whom?

Ans: plan is a strategic document which describes how to perform a task in effective, efficient and optimized way. Test plan prepared by test lead

Seviority and Priority?

Seviority: seviority is nothing but seriousness of the defect

Priority: in what sequence defect has to be rectified

Bug Life Cycle?

Defect life cycle is a cycle which a defect goes through during its lifetime

Bug,Defect,Error,failure-Definitions and Differences?

Error: When we get the wrong output i.e. syntax error, logical error
Fault: When everything is correct but we are not able to get a result
Failure: We are not able to insert any input or after deploying the apln into client environment that time if it is not work then we can say failure

Defect: if it is not working as for the customer expectations

Regression  Testing, Re-Testing,Adhoc Testing--->Definitions?

Regression : It is a type of testing in which one will perform testing on the already tested functionalities again and again.

It is usually done in two scenarios.

1.    Whenever the testers has raised the defects, rectified by the developers and next build is released to the testing department then the test engineer’s will test the defect functionality as well as the related functionality once again.

2.    Whenever some new features are incorporated by the developers, next build is released to the testing department then the test engineers will once again test the related functionalities of the new features in order to confirm that they are working same as previous.

Note: - Testing the new functionalities for the first time is known as new testing but not Regression Testing.

Retesting: It is a type of testing in which one will test the same functionality again and again with different sets of values in order to come to a conclusion whether it is working or not.

Adhoc Testing: It is a type of testing in which one will perform testing on the application in his own style after understanding the requirements clearly.

SDLC(Software Development Life Cycle)---phases?

Six Phases:

 1.Initial phase(or)Requirement phase: in this phase they will gather the customer requirements

2.Analysis Phase: they will analyzing the customer requirements

3.Design Phase: they will divide the whole project

4:Coding phase: they will developing the script based on the customer  requirements

5.Testing phase: we will test the application

6.Delivery and Maintenance phase:

They will install or deployed or delivery the application in the client environment

STLC(Software Testing Life cycle)-----phases?

Six phases:

1.Test Planing: test plan prepared by test lead. test pan having some contents

1.0          Introduction

1.1        Objective

1.2       Reference Document

2.0                Coverage Of Testing

2.1       Features To Be Testing

2.2       Features Not To Be Testing

                   

                   3.0       Test Strategy

3.1       Levels Of Testing

3.2         Types of testing

3.3         Test design techniques

3.4         Configuration management

3.5         Test metrics

3.6         Terminology

3.7         Automation Plan

3.8         List of automated tools

     

4.0           Base criteria

  4.1     Acceptance criteria

                  4.2       Suspension criteria

5.0            Test Deliverable

6.0            Test Environment

7.0            Resource Planning

8.0            Scheduling

9.0            Staffing& Training

10.0          Risks & Contingencies

11.0          Assumptions

12.0          Approval Information

2.Test Development: we will write the test cases based on the customer requirements

3.Test Execution: in this phase we will compare the expected value and actual value

4.Result Analysis: if it is actual value is expected value then we will give status pass

Otherwise we will raise the defect

5.Bug Tracking: Defect life cycle is a cycle which a defect goes through during its lifetime

6.Reporting: we will raise the defect using defect profile template

Levels of Testing:

1.Unit Testing:

Unit is nothing but it is a smallest part of the application.

 It is a level of testing in which one will perform testing on the units. It is a white box testing and usually developers or white box testers will perform.

2.Module Testing:

Module: Module is defined as a group of related functionalities to perform a major task

It is a level of tasting in which one will perform testing on the modules. It is a black box testing and usually test engineers perform it.

3.Integration Testing:

It is a level of testing in which the developers will develop some interfaces to integrate the modules and test whether the interfaces are working fine or not. It is  a  white box testing usually developers or white box tasters perform.

            The developers may follow one of the following approaches while integrating the modules.

            1.Top-down approach

            2.Bottom –up approach

            3.Hybrid or Sandwich approach

            4.Bigbang approach

1.Top-down approach: - In this approach one will develop the parent modules first and then integrate them with the related child modules

2.Bottom-up approach: - In this approach one will develop the child modules first and integrate them to the parent modules

3.Hybrid approach Or Sandwich approach:- This is a mixed approach of both the top down and bottom up approaches

4.Big bang approach:-In this approach one will wait till all the modules are ready and finally they will integrate all the modules at a time

ÞSTUB: - While integrating the modules in top down approach if at all any mandatory module is missing then that module is replace with a temporary program known as STUB

ÞDRIVER: -While integrating the modules in bottom up approach. If at all any mandatory module is missing then that module is replaced with a temporary program known as DRIVER

4.System Level Testing:

It is a level of testing in which one will install the complete application in to the environment and then perform testing on it. At this level different types of testing will be done one among those is system integration testing.

5.User  Acceptence Testing(U.A.B):

It is the level of testing in which one will perform the same system testing in the presence of the user in order to make him accept the application. It is a black box testing and usually Test engineer performs it.

There are two types of user acceptance testing’s available

1)alfa testing

2)beta testing

a- Testing (Alpha Testing): -

             It is a type of user acceptance testing in which the test engineers will test the application in our company, in the presence of the customer.

Advantage: - If at all any defects are found then there is a chance of rectifying them immediately.

 b-Testing (Beta): -

            It is a type of user acceptance testing done in the clients place either by the end-users or by the third party testing experts before actual implementation.

Drawback: If at all any defects are found then there is no chance of rectifying them immediately.

TEST DESIGN TECHNIQS

Technique is something i.e., used for accomplishing a complex task in an easy manner.

Boundary value analysis and equivalence partitioning both are test case design strategies in black box testing.

‘Boundary value analysis’ testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain.

boundry value analysis

For the instance consider the 5 digit mob number which

Starts with 9, so the valid range can be from 90000 to 

99999. Then by boundary value analysis we get 6 input 

Data

1. Input less than lower boundary => 90000-1.

2. Input equals to the lower boundary => 90000.

3. Input greater than the lower boundary =>1 90000+1.

4. Input less than upper boundary => 99999-1.

5. Input equals to the upper boundary => 99999.

6. Input greater than the upper boundary => 99999+1.

 From the above test cases four test (2, 3, 4, and 5) cases will 

Pass the conditions and rest two (1, 6) will fail.

Equivalenceclass partition

In this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce the total number of test cases to a finite set of testable test cases, still covering maximum requirements.

Consider a form field which asks for the age of a person.

Let the age should be >=18 and <=50.

This range can be divided into three classes.

==>> Values less than 18(invalid class)

==>> Values between 18-50(valid class)

==>> value greater than 50(invalid class)

We can see that there are two invalid and one valid class.

It is not necessary that we have to use multiple values 

From each class. One value from each class is more than 

Enough.