2 Manual Testing

Manual Testing Interview Preparation:

MANUAL TESTING3/2/2016

Software Testing:

Definition:

Testing is a process of evaluating the application/system functionality to ensure that it meets the client requirements.

Testing is a process of finding defects in an application.

DEFECT: Mismatching between the actual and expected value is called defect.

-if the functionality of an application is not working as per the requirements of the Client then it’s a defect.

ISSUE: Issues are related to program errors and compilation errors.

BUG: When comes to developer terminology they call defect as bug or Developer accepts defect then it will called as bug.

When the Testing process starts:

Actual Testing process starts after getting the requirements, reviewing the requirements, RTM is prepared, writing Test cases and the build should is ready.

What is BRD?

BRD means Business Requirement Document. It has all the requirements of the client.

Requirements and cost of the project etc.,

Since the document is in Business language so we call it as Customer Requirement Specification (CRS) Document.

BRD/CRS Document is prepared by Business Analyst (BA).

What is SRS?

SRS means System Requirement Specification (SRS) Document.

SRS has details about project application, database, external interface requirements and functional/Non-functional requirements.

Block Box Testing:

Black box testing is done without having the knowledge of application coding.

Based on client requirement and functionality black box testing can be done.

White Box Testing:

White box testing is done with the Internal Coding knowledge of the application.

Which include Code Statements, functions and conditions as per the business requirement.


LEVELS OF TESTING:

-Functional Testing

-Integration Testing

-System Testing

-Regression Testing

-UAT Testing

Unit Testing:

Testing an individual software module/unit is called unit testing.

Mostly done by the development team to check the coding.

Sanity Testing:

Sanity Testing is done to check the application stability whether it can be tested for further before functional testing starts.

And to check basic things like GUI functionality and Connectivity between application and Database etc. based on the business requirement.

Smoke Testing:

Smoke Testing is conducted to check the normal working of the build to make sure if it is possible to continue testing. It is done in the beginning of the software testing cycle.

Functional Testing:

Functional testing is done to check modules, components and functionality of the application.

Integration Testing:

After combining all the modules and testing these modules to make sure that they are working fine as per the business requirements.

Test cases are developed to test the interface between the individual modules.

Up Stream and Down Stream:

Upstream means Data transfer from source system to ETL

Downstream means Data Generated from ETL

Regression Testing:

Regression Testing is to check whether the application/build existing functionality is remains same when the build is modified by adding some new functionalities to the existing build.

*Here we consider a highly sensitive test cases and by executing these test cases we perform regression testing.


System Testing:

System Testing is performed to check the completeness of the application and all the requirements like software and hardware as per the client requirements.

Software System Testing testers are concentrated on finding bugs/defects based on software application behavior, software design and expectation of end user.

Why system testing is important:

a) In Software Development Life Cycle the System Testing is perform as the first level of testing where the System is tested as a whole.

b) In this step of testing check if system meets functional requirement or not.

c) System Testing enables you to test, validate and verify both the Application Architecture and Business requirements.

d) The application/System is tested in an environment that particularly resembles the effective production environment where the application/software will be lastly deployed.

Generally, a separate and dedicated team is responsible for system testing. And, System Testing is performed on staging server which is similar to production server. So this means you are testing software application as good as production environment.

*system testing is conducted after the integration testing.

UAT Testing:

Testing performed to ensure that the application meets the client requirements before the release of the application into market.

Here we conduct two levels of testing.

Alpha: Testing an application by test team in the presence of the End user within the organization to let the end user to know that the application is working as per the requirements.

Beta: Testing an application by the end user in the client server to ensure that the application is working as per the client requirements.

End-to-end Testing:

Just like system testing.

Testing the application from Requirement analysis phase to User Acceptance phase to ensure that the process flow of the application is working well as per the client requirements.

For this, after integrating all the system components we pass right information to check the stability of the application as per the business requirements.

Re-Testing:


If a Defect is raised by the tester and is fixed by the Developer then Tester should test the same functionality again to make sure that Defect is fixed or not.

WHEN THE TESTING PROCESS STOPPED?

-All the test cases passed

-Rate of bug finding in an application falls to a certain level

-Testing Budget is depleted

-Testing Deadlines are reached

-All the requirements are tested

Traceability Matrix:

Defines the Mapping between the client requirements and test cases prepared by the tester. Traceability Matrix is used by test team to verify how far the test cases prepared and covered requirements of the functionalities to be tested.

DEFECT LIFE CYCLE:

Definition: When the defect is detected for the first time then tester will assign the status as NEW.

Then the developer will check and accepts that the raised defect is true then he gives the status as OPEN.

After fixing the defect the developer will send it to the tester. And then the tester will set the status as CLOSED if the defect is fixed or he will set the status as Re-Open.

If the defect is assigned to developer by the tester, then if the defect is not intended to fix in the current release and development team will going to fix in the next release then the developer/tester will set the status as DIFFERED.

If the developer is sure about that the raised defect is not a genuine defect or already raised by the tester or tester mistake to raise a bug then he will set the status as REJECT

When the developer fixes a defect then he will give the status as FIXED.

SEVERITY:

How seriously the defect is impacting the Application.

PRIORITY:

Priority is the order in which the developer has to fix the Bug.

Show Stopper Issue:

An issue that won’t allow the test team to test the application to further levels.

After fixing the show stopper issue then only we can go for further to test the application.


What are the Defect contents?

A clear description about the bug and that should be understandable to developer.

-Defect ID

-Defect status

-Defects Summary

-Assigned to Developer

-Description to reproduce the bug

-Expected Results

-Actual Results

-Tester Name

-Severity & Priority

-Attachments

What is a Test Plan?

Test Plan is a document which holds the description about scope, objectives and approach for software testing. Usually prepared during the early phase of the project.

-Introduction of objects

-Scope

-Test strategy

-Test Environment

-Modules to be tested

-Modules not to be tested

-Schedule

-Test Entry Criteria (Test cases Reviewed / Documents are available/ Test Environment is set)

-Test Exit Criteria (No defects/ High Severity bugs fixed/ Deliverables are ready)

-Resource Allocation Details.

What is Test Case?

Test case is a document which specifies the input values and expected outputs and preconditions to test an application /software functionality.

Software Development Life Cycle (SDLC):


Software Development Life Cycle has six levels.

*Gathering Requirements

*Analysis

*Design Phase

*Coding

*Testing

*Release & Maintenance

Software Testing Life Cycle (STLC):

Software Life Cycle has six levels

-Test Planning

-Test Analysis

-Test Design

-Test Execution

-Defect Tracking

-Reporting

What is Test Strategy?

A Test Strategy document is a high level document and normally developed by project manager. This document defines Software Testing Approach to achieve testing objectives. The Test Strategy is normally derived from the Business Requirement Specification document (BRD).

Criteria for writing test cases:

*All the requirements should be understood and reviewed

*Test case template document should be ready

*All the requirements should be documented and relevant test cases should covered.