Software Testing Trainning - Day4

8/14/2019 Software Testing Trainning - Day4

1/24

Types of Testing. Testing LifeTypes of Testing. Testing Life

cycle, Bug Life cyclecycle, Bug Life cycle

Day 4-Session 1Lavanya.M


2/24

Test Plan

Test Design

Test Execution

Test Log

Defect Tracking

Report Generation.

Software Testing LifeSoftware Testing Life

cyclecycle


3/24

Testing PlanTesting PlanDuring this phase Test Strategy, Test Plan, Test Bed willbe created.A test plan is a systematic approach in testing a system orsoftware.The plan should identify:

Which aspects of the system should be tested?

Criteria for success.

The methods and techniques to be used.

Personnel responsible for the testing.

Different Test phase and Test Methodologies

Manual and Automation Testing

Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc

Evaluation & identification Test, Defect tracking tools


4/24

Test DesignTest Design

During this phase

Test Scenarios will be identified.

Test Cases will be prepared. Test data and Test scripts prepared.

Test case reviews will be conducted.


5/24

Test ExecutionTest Execution

Testers execute the software based on the plansand test.

Test cases will be executed.

Test Scripts will be tested.


6/24

Test LogTest Log

A chronological record of all relevant details aboutthe execution of a test.

Test Results will be analyzed


7/24

Defect TrackingDefect Tracking

Capture, review and analyze Test Results

Raised the defects and tracking for its closure


8/24

Test summary reports

Test Metrics and process Improvements made

Build release

Receiving acceptance

Report Generation.Report Generation.


9/24

Bug Life CycleBug Life Cycle


10/24

Types of TestingTypes of Testing

Black Box Testing White Box Testing

Unit Testing

Incremental Integration Testing

Integration Testing Functional Testing

System Testing

End-to-End Testing

Sanity Testing Regression Testing

Acceptance Testing

Load Testing

Stress Testing

Performance Testing

List of the different types of testing that can be implemented are listed below which

will be followed by explanations of the same

Usability Testing

Install / Uninstall Testing

Recovery Testing

Security Testing

Compatibility Testing

Exploratory Testing

Ad-hoc Testing

Comparison Testing

Alpha Testing

Beta Testing

Mutation Testing

Conformance Testing

Quality Assurance Testing


11/24


12/24

White Box TestingWhite Box Testing

It can also be termed as Structural TestingTests that verify the structure of the software and require complete

access to the objects source code is white box testing

It is known as white box as all internal workings of the code can be

seenWhite-box tests make sure that the software structure itself contributesto proper and efficient program execution

It is based in of the internal logic of an applications code and tests are

based on coverage of code statements, branches, paths, conditionsIn this type of testing code needs to be examined by highly skilledtechnicians

Test if a component conforms to design


13/24

FunctionalityFunctionality

TestingTesting

It is black-box testing geared to functional requirements and should bedone by testers

Testing done to ensure that the product functions the way it is designed to

according to the design specifications and documentation

This testing can involve testing of products user interface, databasemanagement, security, installation, networking, etc.


14/24

Sanity TestingSanity Testing

Initial testing effort to determine if a new software version is performing wellenough to accept it for a major testing effort.

For example, if the new software is crashing systems every 5 minutes,bogging down systems to a crawl, or destroying databases, the softwaremay not be in a 'sane' enough condition to warrant further testing in itscurrent state.


15/24

Regression TestingRegression Testing

This is re-testing of the product/software to ensure that all reported bugshave been fixed and implementation of changes has not affected otherfunctions

It is always difficult to the amount of re-testing required, especially when thesoftware is at the end of the development cycle

These tests apply to all phases wherever changes are being made

This testing also ensures reported product defects have been corrected for

each new release and that no new quality problems were introduced in themaintenance process


16/24


17/24

Stress TestingStress TestingThis term is more often used interchangeably with load andperformance testing.

It is system functional testing while under unusually heavy loads, heavyrepetition of certain actions or inputs, input of large numerical values,large complex queries to a database system

Always aimed at finding the limits at which the system will fail through

abnormal quantity or frequency of inputs.Examples could be:-

higher rates of inputs

data rates an order of magnitude above normal

test cases that require maximum memory or other resources test cases that cause thrashing in a virtual operating system

test cases that cause excessive hunting for data on disk systems

This testing can also attempt to determine combinations of otherwise

normal inputs can cause improper processing


18/24

PerformancePerformance

TestingTesting

This term is more often used interchangeably with stress and load testing

To understand the applications scalability, or to benchmark the performancein a environment or to identify the bottlenecks in high hit-rate Web sites, thistesting can be used

This testing checks the run-time performance in the context of the integratedsystem

This may require special software instrumentation

Ideally, these types of testing are defined in requirements documentation orQA or Test Plans.


19/24

Usability TestingUsability Testing

This testing is testing for user-friendliness

The target will always be the end-user or customer

Techniques such as interviews, surveys, video recording of user sessionscan be used in this type of testing

Programmers and Testers are not appropriate as usability testers


20/24

Install/UninstallInstall/Uninstall

TestingTesting

Testing of full, partial, or upgrade install/uninstall processes The target wilalways be the end-user or customer


21/24

CompatibilityCompatibility

TestingTesting

Testing whether the software is compatible in particular hardware / software /

operating system / network / etc. environment


22/24

Alpha TestingAlpha Testing

This is testing of an application when development is nearingcompletion;mostly testing conducted at the developers site by a customer

The customer uses the software with the developer looking over theshoulder and recording errors and usage problems

Testing is conducted in a controlled environment

Minor design changes can be still made as a result of this testing

Typically conducted by end-users or customers and not by programmersor testers


23/24

Beta TestingBeta Testing

Testing conducted when development and testing are completed and bugsand problems need to be found before final release

It is live testing in an environment not controlled by the developer.

Customer records the errors / problems reports difficulties at regular

intervalsTesting is conducted at one or more customer sites

Typically conducted by end-users or customers and not by programmersor testers


24/24

ExerciseExercise Testing efforts should be started only after the coding

is completed. True/False

Software testing efforts aim at preventing bugs. - True/False

During the Construction phase in the life cycle, both

functional and structural Test data should be generated and

applied. - True/False

The data that is generated for Statement testing, Branch

Testing and path testing is known as ____________

Explain in your own words about

Boundary value analysis

Equivalence Partitioning

Software Testing Trainning - Day4

Documents

Transcript of Software Testing Trainning - Day4