Testing

What is Testing?
1. Testing is the process of evaluating a system or its component(s) with the intent to find
whether it satisfies the specified requirements or not.
2. In another words, testing is executing a system in order to identify any gaps, errors, or
missing requirements in contrary to the actual requirements.
3. According to ANSI/IEEE 1059 standard,
4. Testing can be defined as - A process of analyzing a software item to detect the differences
between existing and required conditions (i.e.defects/errors/bugs) and evaluate the features
of the software item.

Who does Testing?

1. It depends on the process and the associated stakeholders of the project(s).

2. In the IT industry, large companies have a team with responsibilities to evaluate the
developed software in context of the given requirements.
3. Moreover, developers also conduct testing which is called Unit Testing.
4. In most cases, the following professionals are involved in testing a system within their
respective capacities −

 Software Tester

 Software Developer

 Project Lead/Manager

 End User

5. Different companies have different designations for people who test the software on the
basis of their experience and knowledge such as Software Tester,
6. Software Quality Assurance Engineer, QA Analyst, etc.
7. It is not possible to test the software at any time during its cycle. The next two sections state
when testing should be started and when to end it during the SDLC.
When to Start Testing?

1. An early start to testing reduces the cost and time to rework and produce error-free software
that is delivered to the client.

2. However in Software Development Life Cycle (SDLC), testing can be started from the
Requirements Gathering phase and continued till the deployment of the software.

3. It also depends on the development model that is being used.

4. For example, in the Waterfall model, formal testing is conducted in the testing phase; but in
the incremental model.

5. Testing is performed at the end of every increment/iteration and the whole application is
tested at the end.

6. Testing is done in different forms at every phase of SDLC −

 During the requirement gathering phase, the analysis and verification of requirements are
also considered as testing.

 Reviewing the design in the design phase with the intent to improve the design is also
considered as testing.

 Testing performed by a developer on completion of the code is also categorized as

testing.

When to Stop Testing?

1. It is difficult to determine when to stop testing, as testing is a never-ending process and no

one can claim that a software is 100% tested.

2. The following aspects are to be considered for stopping the testing process −

 Testing Deadlines

 Completion of test case execution

 Completion of functional and code coverage to a certain point

 Bug rate falls below a certain level and no high-priority bugs are identified
  Management decision

Introduction of Testing?
1. Software testing is an activity to check whether the actual results match the expected
results and to ensure that the software system is Defect free. It involves execution of a
software component or system component to evaluate one or more properties of interest.
2. Software testing can be stated as the process of verifying and validating that a software or
application is bug free, meets the technical requirements as guided by it’s design and
development and meets the user requirements effectively and efficiently with handling all
the exceptional and boundary cases.

3. The process of software testing aims not only at finding faults in the existing software but
also at finding measures to improve the software in terms of efficiency, accuracy and
usability. It mainly aims at measuring specification, functionality and performance of a
software program or application.

4. Software testing also helps to identify errors, gaps or missing requirements in to the
actual requirements.

5. It can be either done manually or using automated tools.

6. Some prefer saying Software testing as a white box and Black Box Testing.

 Software Testing Important?

1. Testing is important because software bugs could be expensive or even dangerous.

2. Software bugs can potentially cause monetary and human loss, history is full of such

 What are different types of software testing?

Software Testing can be broadly classified into two types:

1. Manual Testing

2. Automation Testing
  Manual Testing:

1. Manual testing includes testing a software manually, i.e., without using any automated
tool or any script.
2. In this type, the tester takes over the role of an end-user and tests the software to identify
any unexpected behavior or bug.
3. There are different stages for manual testing such as unit testing, integration testing,
system testing, and user acceptance testing.
4. Testers use test plans, test cases, or test scenarios to test a software to ensure the
completeness of testing.
5. Manual testing also includes exploratory testing, as testers explore the software to
identify errors in it.

 Automation Testing: 
1. Automation testing, which is also known as Test Automation.
2. When the tester writes scripts and uses another software to test the product.This process
involves automation of a manual process.
3. Automation Testing is used to re-run the test scenarios that were performed manually,
quickly, and repeatedly.

4. The regression testing, automation testing is also used to test the application from load
testing, performance testing, and stress testing point of view.
 5. It increases the test coverage, improves accuracy, and saves time and money in
comparison to manual testing.

What to Automate?

 It is not possible to automate everything in a software.

 The areas at which a user can make transactions such as the login form or registration
forms,

 any area where large number of users can access the software simultaneously should be
automated.

 All GUI items, connections with databases, field validations, etc. can be efficiently
tested by automating the manual process.

When to Automate?

Test Automation should be used by considering the following aspects of a software −

 Large and critical projects

 Projects that require testing the same areas frequently

 Requirements not changing frequently

 Accessing the application for load and performance with many virtual users

 Stable software with respect to manual testing

 Availability of time

How to Automate?

 Automation is done by using a supportive computer language like VB scripting and an

automated software application.
 There are many tools available that can be used to write automation scripts.

 Before mentioning the tools, let us identify the process that can be used to automate the
testing process −
  Identifying areas within a software for automation

 Selection of appropriate tool for test automation

 Writing test scripts

 Development of test suits

 Execution of scripts

 Create result reports

 Identify any potential bug or performance issues

 What are different levels of software testing?

 Software Testing - Levels

 There are different levels during the process of testing.

 Levels of testing include different methodologies that can be used while conducting
software testing.

 The main levels of software testing are −

 Functional Testing

 Non-functional Testing

The main levels of software testing are follows:

1. Functional Testing

2. Non-functional Testing

 Functional Testing
 This is a type of black-box testing that is based on the specifications of the software that
is to be tested.

 Functional testing of a software is conducted on a complete, integrated system to

evaluate the system's compliance with its specified requirements.
  This is a type of black-box testing that is based on the specifications of the software that
is to be tested.

 The application is tested by providing input and then the results are examined that need
to conform to the functionality it was intended for.

 Functional testing of a software is conducted on a complete, integrated system to

evaluate the system's compliance with its specified requirements.

 There are five steps that are involved while testing an application for functionality.

 An effective testing practice will see the above steps applied to the testing policies of
every organization and hence

 it will make sure that the organization maintains the strictest of standards when it comes
to software quality.

 Black Box Testing: 

 The technique of testing in which the tester doesn’t have access to the source code of the
software and is conducted at the software interface without concerning with the internal
logical structure of the software is known as black box testing.
 The technique of testing without having any knowledge of the interior workings of the
application is called black-box testing.
 The tester is oblivious to the system architecture and does not have access to the source
code.

 Typically, while performing a black-box test, a tester will interact with the system's user
interface by providing inputs and examining outputs without knowing how and where
the inputs are worked upon.

There are five steps that are involved while testing an application for functionality.

 The determination of the functionality that the intended application is meant to

perform.

 The creation of test data based on the specifications of the application.

 The output based on the test data and the specifications of the application.
  The writing of test scenarios and the execution of test cases.

 The comparison of actual and expected results based on the executed test cases.

 It is used for validation.

 In this we ignores internal working mechanism and

 focuses on what is the output?.

The following are the advantages and disadvantages of black-box testing.

 Advantage of Black Box Testing

1. Well suited and efficient for large code segments.

2. Code access is not required.

3. Clearly separates user's perspective from the developer's perspective through visibly
defined roles.

4. Large numbers of moderately skilled testers can test the application with no knowledge
of implementation, programming language, or operating systems

 Disadvantage of Black Box Testing

1. Limited coverage, since only a selected number of test scenarios is actually performed.

2. Inefficient testing, due to the fact that the tester only has limited knowledge about an
application.

3. Blind coverage, since the tester cannot target specific code segments or errorprone areas.

4. The test cases are difficult to design.

 Non-functional testing

1. Non-functional testing is done to verify the non-functional requirement i.e. Performance,

Usability etc.
 2. It verifies if the behavior of the system is as per the requirement or not.

3. It covers all the aspects which are not covered in functional testing.

4. This section is based upon testing an application from its non-functional attributes.

5. Non-functional testing involves testing a software from the requirements which are
nonfunctional in nature but important such as performance, security, user interface, etc.

White-Box Testing: 
1. The technique of testing in which the tester is aware of the internal workings of the
product have access to it’s source code and is conducted by making sure that all internal
operations are performed according to the specifications is known as white box testing.
2. White-box testing is the detailed investigation of internal logic and structure of the code.
3. White-box testing is also called glass testing or open-box testing.
4. In order to perform white-box testing on an application, a tester needs to know the
internal workings of the code.

5. The tester needs to have a look inside the source code and find out which unit/chunk of
the code is behaving inappropriately.

 Advantages of White box Testing

1. As the tester has knowledge of the source code, it becomes very easy to find out which
type of data can help in testing the application effectively.
2. It helps in optimizing the code.

3. Extra lines of code can be removed which can bring in hidden defects

4. Due to the tester's knowledge about the code, maximum coverage is attained during test
scenario writing.

 Disadvantages of White box Testing

1. Due to the fact that a skilled tester is needed to perform white-box testing, the costs are
increased.
 2. Sometimes it is impossible to look into every nook and corner to find out hidden errors
that may create problems, as many paths will go untested.

3. It is difficult to maintain white-box testing, as it requires specialized tools like code

analyzers and debugging tools.

Grey-Box Testing

 Grey-box testing is a technique to test the application with having a limited knowledge
of the internal workings of an application.

 In software testing, the phrase the more you know, the better carries a lot of weight
while testing an application.

 Mastering the domain of a system always gives the tester an edge over someone with
limited domain knowledge.

 Unlike black-box testing, where the tester only tests the application's user interface; in
grey-box testing

 the tester has access to design documents and the database.

 Having this knowledge, a tester can prepare better test data and test scenarios while
making a test plan.

Advantages of Grey Box Testing

 Offers combined benefits of black-box and white-box testing wherever possible.

 Grey box testers don't rely on the source code; instead they rely on interface definition
and functional specifications.

 Based on the limited information available, a grey-box tester can design excellent test
scenarios especially around communication protocols and data type handling.

 The test is done from the point of view of the user and not the designer.

Disadvantages of Grey Box Testing

  Since the access to source code is not available, the ability to go over the code and test
coverage is limited.

 The tests can be redundant if the software designer has already run a test case.

 Testing every possible input stream is unrealistic because it would take an unreasonable
amount of time; therefore, many program paths will go untested.

 Comparison of Testing Methods

The difference between black-box testing, grey-box testing, and white-box testing.

Black-Box Testing Grey-Box Testing White-Box Testing

The internal workings of an The tester has limited knowledge Tester has full knowledge of
application need not be known. of the internal workings of the the internal workings of the
application. application.

Also known as closed-box Also known as translucent testing, Also known as clear-box
testing, data-driven testing, or as the tester has limited testing, structural testing, or
functional testing. knowledge of the insides of the code-based testing.
application.

Performed by end-users and Performed by end-users and also Normally done by testers and
also by testers and developers. by testers and developers. developers.

Testing is based on external Testing is done on the basis of Internal workings are fully
expectations - Internal behavior high-level database diagrams and known and the tester can
of the application is unknown. data flow diagrams. design test data accordingly.
It is exhaustive and the least Partly time-consuming and The most exhaustive and
time-consuming. exhaustive. time-consuming type of
testing.

Not suited for algorithm Not suited for algorithm testing. Suited for algorithm testing.
testing.

This can only be done by trial- Data domains and internal Data domains and internal
and-error method. boundaries can be tested, if boundaries can be better
known. tested.

Different Levels of Software Testing

 Unit Testing: 

1. A level of the software testing process where individual units/components of a

software/system are tested.

2. The purpose is to validate that each unit of the software performs as designed.

3. It focuses on smallest unit of software design. In this we test an individual unit or group
of inter related units.

4. It is often done by programmer by using sample input and observing its corresponding
outputs.

5. This type of testing is performed by developers before the setup is handed over to the
testing team to formally execute the test cases.

6. Unit testing is performed by the respective developers on the individual units of source
code assigned areas.
7. The developers use test data that is different from the test data of the quality assurance
team.

8. The goal of unit testing is to isolate each part of the program and show that individual
parts are correct in terms of requirements and functionality.

 Limitations of Unit Testing

1. Testing cannot catch each and every bug in an application.

2. It is impossible to evaluate every execution path in every software application. The same
is the case with unit testing.

3. There is a limit to the number of scenarios and test data that a developer can use to verify
a source code.

4. After having exhausted all the options, there is no choice but to stop unit testing and
merge the code segment with other units.

 Integration Testing:

1. A level of the software testing process where individual units are combined and tested as
a group.
2. The purpose of this level of testing is to expose faults in the interaction between
integrated units.
3. Integration testing are of two types: (i) Top down (ii) Bottom up
4. Integration testing is defined as the testing of combined parts of an application to
determine if they function correctly.

5. Integration testing can be done in two ways: Bottom-up integration testing and Top-
down integration testing.

 Bottom-up integration

1. This testing begins with unit testing, followed by tests of progressively higher-
level combinations of units called modules or builds.
  Top-down integration

1. The highest-level modules are tested first and progressively, lower-level modules
are tested thereafter.

6. In a comprehensive software development environment, bottom-up testing is usually

done first, followed by top-down testing.

7. The process concludes with multiple tests of the complete application, preferably in
scenarios designed to mimic actual situations

 System Testing:

1. A level of the software testing process where a complete, integrated system/software is

tested.
2. The purpose of this test is to evaluate the system’s compliance with the specified
requirements.
3. System testing tests the system as a whole. Once all the components are integrated, the
application as a whole is tested.
4. This type of testing is performed by a specialized testing team.
System testing is important because of the following reasons −

 System testing is the first step in the Software Development Life Cycle, where the
application is tested as a whole.

 The application is tested thoroughly to verify that it meets the functional and technical
specifications.

 The application is tested in an environment that is very close to the production

environment where the application will be deployed.

 System testing enables us to test, verify, and validate both the business requirements as
well as the application architecture.

 Acceptance Testing: 
1. A level of the software testing process where a system is tested for acceptability.
 2. The purpose of this test is to evaluate the system’s compliance with the business
requirements and assess whether it is acceptable for delivery.
3. This is arguably the most important type of testing, as it is conducted by the
Quality Assurance Team who will gauge whether the application meets the
intended specifications and satisfies the client’s requirement.
4. The QA team will have a set of pre-written scenarios and test cases that will be
used to test the application.
5. More ideas will be shared about the application and more tests can be performed
on it to gauge its accuracy and the reasons why the project was initiated.
6. Acceptance tests are not only intended to point out simple spelling mistakes,
cosmetic errors, or interface gaps, but also to point out any bugs in the application
that will result in system crashes or major errors in the application.
7. performing acceptance tests on an application, the testing team will reduce how
the application will perform in production.
8. There are also legal and contractual requirements for acceptance of the system.

 Regression Testing

1. Every time new module is added leads to changes in program.

 2. This type of testing make sure that whole component works properly even after adding
components to the complete program.

3. Whenever a change in a software application is made, it is quite possible that other areas
within the application have been affected by this change.

4. Regression testing is performed to verify that a fixed bug hasn't resulted in another
functionality or business rule violation.

5. The intent of regression testing is to ensure that a change, such as a bug fix should not
result in another fault being uncovered in the application.

Regression testing is important because of the following reasons −

 Minimize the gaps in testing when an application with changes made has to be tested.

 Testing the new changes to verify that the changes made did not affect any other area of
the application.

 Mitigates risks when regression testing is performed on the application.

 Test coverage is increased without compromising timelines.

 Increase speed to market the product

 Smoke Testing

1. This test is done to make sure that software under testing is ready or stable for further
testing

2. It is called smoke test as testing initial pass is done to check if it did not catch the fire or
smoked in the initial switch on.

 Alpha Testing

1. This is a type of validation testing.It is a type of acceptance testing which is done

before the product is released to customers.

2. It is typically done by QA people.

 3. This test is the first stage of testing and will be performed amongst the teams
(developer and QA teams).

4. Unit testing, integration testing and system testing when combined together is
known as alpha testing.

5. During this phase, the following aspects will be tested in the application −

 Spelling Mistakes

 Broken Links

 Cloudy Directions

 The Application will be tested on machines with the lowest specification to test loading times and any
latency problems.

 Beta Testing
1. The beta test is conducted at one or more customer sites by the end-user of the
software.

2. This version is released for the limited number of users for testing in real time
environment

3. This test is performed after alpha testing has been successfully performed. In beta
testing, a sample of the intended audience tests the application. Beta testing is also
known as pre-release testing.

4. Beta test versions of software are ideally distributed to a wide audience on the
Web, partly to give the program a "real-world" test and partly to provide a
preview of the next release.

Phases of Beta testing following −

 Users will install, run the application and send their feedback to the project team.

 Typographical errors, confusing application flow, and even crashes.

 Getting the feedback, the project team can fix the problems before releasing the software to the actual
users.
  The more issues you fix that solve real user problems, the higher the quality of your application will
be.

 Having a higher-quality application when you release it to the general public will increase customer
satisfaction.

 Performance Testing

 Performance testing is considered as one of the important and mandatory testing type in
terms of the following aspects –

 It is mostly used to identify any bottlenecks or performance issues rather than finding
bugs in a software.

 There are different causes that contribute in lowering the performance of a software −

 Speed (i.e. Response Time, data rendering and accessing)

 Capacity

 Stability

 Scalability

 Performance testing can be either qualitative or quantitative and can be divided into
different sub-types such as Load testing and Stress testing.

a) Load Testing

1. It is a process of testing the behavior of a software by applying maximum load in terms of

software accessing and manipulating large input data.

2. It can be done at both normal and peak load conditions.

3. This type of testing identifies the maximum capacity of software and its behavior at peak
time.

4. Most of the time, load testing is performed with the help of automated tools such as Load
Runner, AppLoader, IBM Rational Performance Tester, Apache JMeter, Silk Performer,
Visual Studio Load Test, etc.
5. Virtual users (VUsers) are defined in the automated testing tool and the script is executed to
verify the load testing for the software.

6. The number of users can be increased or decreased concurrently or incrementally based

upon the requirements

B) Stress Testing

1. The Stress Testing gives unfavorable conditions to the system and check how they perform in
those condition.

2. Stress testing includes testing the behavior of a software under abnormal conditions.

3. The aim of stress testing is to test the software by applying the load to the system and taking
over the resources used by the software to identify the breaking point.

4. This testing can be performed by testing different scenarios such as −

 Shutdown or restart of network ports randomly

 Turning the database on or off

 Running different processes that consume resources such as CPU, memory, server, etc.

 Usability Testing
a. Usability testing is a black-box technique and is used to identify any error(s) and
improvements in the software by observing the users through their usage and
operation.

b. The usability testing can be defined in terms of five factors, i.e. efficiency of use,
learn-ability, memory-ability, errors/safety, and satisfaction.

c. The usability of a product will be good and the system is usable if it possesses the
above factors.
 d. There are some standards and quality models and methods that define usability in
the form of attributes and sub-attributes such as ISO-9126, ISO-9241-11, ISO-
13407, and IEEE std.610.12, etc.

 UI vs Usability Testing
1. UI testing involves testing the Graphical User Interface of the Software.

2. UI testing ensures that the GUI functions according to the requirements and tested in terms
of color, alignment, size, and other properties.

On the other hand,

1. Usability testing ensures a good and user-friendly GUI that can be easily handled.

2. UI testing can be considered as a sub-part of usability testing.

 Security Testing
Security testing involves testing a software in order to identify any flaws and gaps from security
and vulnerability point of view.

The aspect of security testing are as follows:

 Confidentiality

 Integrity

 Authentication

 Availability

 Authorization

 Non-repudiation

 Software is secure against known and unknown vulnerabilities

 Software data is secure

 Software is according to all security regulations

 Input checking and validation

 SQL insertion attacks

  Injection flaws

 Session management issues

 Cross-site scripting attacks

 Buffer overflows vulnerabilities

 Directory traversal attacks

 Portability Testing
1. Portability testing includes testing a software with the aim to ensure its reusability and that it
can be moved from another software as well.

2. Following are the strategies that can be used for portability testing −

 Transferring an installed software from one computer to another.

 Building executable (.exe) to run the software on different platforms.

3. Portability testing can be considered as one of the sub-parts of system testing, as this testing
type includes overall testing of a software with respect to its usage over different
environments.

4. Computer hardware, operating systems, and browsers are the major focus of portability
testing. Some of the pre-conditions for portability testing are as follows −

 Software should be designed and coded, keeping in mind the portability requirements.

 Unit testing has been performed on the associated components.

 Integration testing has been performed.

 Test environment has been established.

5. Testing documentation involves the documentation of artifacts that should be developed

before or during the testing of Software.

6. Documentation for software testing helps in estimating the testing effort required, test
coverage, requirement tracking/tracing, etc.

 Test Plan
  Test Scenario

 Test Case

 Traceability Matrix

Principles of Testing:-

1. All the test should meet the customer requirements

2. To make our software testing should be performed by third party

3. Exhaustive testing is not possible.As we need the optimal amount of testing based on the
risk assessment of the application.

4. All the test to be conducted should be planned before implementing it

5. It follows pareto rule(80/20 rule) which states that 80% of errors comes from 20% of
program components.

6. Start testing with small parts and extend it to large parts.

 Software testing can be divided into two steps:

1. Verification: it refers to the set of tasks that ensure that software correctly implements
a specific function.

2. Validation: it refers to a different set of tasks that ensure that the software that has
been built is traceable to customer requirements.
Verification: “Are we building the product right?”
Validation: “Are we building the right product?”

 Differences between verification and validation

Verification Validation

1. Verification addresses the concern: "Are you Validation addresses the concern: "Are
 building it right?" you building the right thing?"

2. Ensures that the software system meets all the Ensures that the functionalities meet the
functionality. intended behavior.

3. Verification takes place first and includes the Validation occurs after verification and
checking for documentation, code, etc. mainly involves the checking of the
overall product.

4. Done by developers. Done by testers.

5. It has static activities, as it includes collecting It has dynamic activities, as it includes

reviews, walkthroughs, and inspections to verify a executing the software against the
software. requirements.

6. It is an objective process and no subjective It is a subjective process and involves

decision should be needed to verify a software. subjective decisions on how well a
software works.

Software Testing - Documentation

 Testing documentation involves the documentation of artifacts that should be developed

before or during the testing of Software.

 Documentation for software testing helps in estimating the testing effort required, test
coverage, requirement tracking/tracing, etc.

 This section describes some of the commonly used documented artifacts related to
software testing such as −

 Test Plan

 Test Scenario
  Test Case

 Traceability Matrix

 Test Plan
1. A test plan outlines the strategy that will be used to test an application

2. The resources that will be used, the test environment in which testing will be performed,
and the limitations of the testing and the schedule of testing activities.

3. Typically the Quality Assurance Team Lead will be responsible for writing a Test Plan.

4. A test plan includes the following −

 Introduction to the Test Plan document

 Assumptions while testing the application

 List of test cases included in testing the application

 List of features to be tested

 What sort of approach to use while testing the software

 List of deliverables that need to be tested

 The resources allocated for testing the application

 Any risks involved during the testing process

 A schedule of tasks and milestones to be achieved

 Test Scenario
1. It is a one line statement that notifies what area in the application will be tested.

2. Test scenarios are used to ensure that all process flows are tested from end to end.

3. A particular area of an application can have as little as one test scenario to a few hundred
scenarios depending on the magnitude and complexity of the application.
4. The terms 'test scenario' and 'test cases' are used interchangeably, however a test scenario
has several steps, whereas a test case has a single step.

5. Viewed from this perspective, test scenarios are test cases, but they include several test
cases and the sequence that they should be executed.

 Test Case
1. Test cases involve a set of steps, conditions, and inputs that can be used while
performing testing tasks.

2. The main intent of this activity is to ensure whether a software passes or fails in
terms of its functionality and other aspects.

3. There are many types of test cases such as functional, negative, error, logical test
cases, physical test cases, UI test cases, etc.

4. test cases are written to keep track of the testing coverage of a software.

5. There are no formal templates that can be used during test case writing.

6. However, the following components are always available and included in every
test case −

 Test case ID

 Product module
  Product version

 Revision history

 Purpose

 Assumptions

 Pre-conditions

 Steps

 Expected outcome

 Actual outcome

 Post-conditions

Many test cases can be derived from a single test scenario. In addition, sometimes multiple test
cases are written for a single software which are collectively known as test suites.

 Traceability Matrix

Traceability Matrix (also known as Requirement Traceability Matrix - RTM) is a table that is
used to trace the requirements during the Software Development Life Cycle. It can be used for
forward tracing (i.e. from Requirements to Design or Coding) or backward (i.e. from Coding to
Requirements). There are many user-defined templates for RTM.

Each requirement in the RTM document is linked with its associated test case so that testing can
be done as per the mentioned requirements. Furthermore, Bug ID is also included and linked
with its associated requirements and test case. The main goals for this matrix are −

 Make sure the software is developed as per the mentioned requirements.

 Helps in finding the root cause of any bug.

 Helps in tracing the developed documents during different phases of SDLC.

Software Testing - Estimation Techniques

Estimating the efforts required for testing is one of the major and important tasks in SDLC.
Correct estimation helps in testing the software with maximum coverage. This section describes
some of the techniques that can be useful in estimating the efforts required for testing.

Functional Point Analysis

This method is based on the analysis of functional user requirements of the software with the
following categories −

 Outputs

 Inquiries

 Inputs

 Internal files

 External files

Test Point Analysis

This estimation process is used for function point analysis for black-box or acceptance testing.
The main elements of this method are: Size, Productivity, Strategy, Interfacing, Complexity,
and Uniformity.

Mark-II Method

It is an estimation method used for analyzing and measuring the estimation based on end-user’s
functional view. The procedure for Mark-II method is as follows −

 Determine the viewpoint

 Purpose and type of count

 Define the boundary of count

 Identify the logical transactions

  Identify and categorize data entity types

 Count the input data element types

 Count the functional size

Miscellaneous

You can use other popular estimation techniques such as −

 Delphi Technique

 Analogy Based Estimation

 Test Case Enumeration Based Estimation

 Task (Activity) based Estimation

 IFPUG method

 Software Testing Tools

The following tools can be used for automation testing −

 HP Quick Test Professional

 Selenium

 IBM Rational Functional Tester

 SilkTest

 TestComplete

 Testing Anywhere

 WinRunner

 LoadRunner

 Visual Studio Test Professional

 WATIR
  Testing and Debugging
Testing –

1. It involves identifying bug/error/defect in a software without correcting it.

2. Normally professionals with a quality assurance background are involved in bugs

identification.

3. Testing is performed in the testing phase.

Debugging 

1. It involves identifying, isolating, and fixing the problems/bugs.

2. Developers who code the software conduct debugging upon encountering an error in the
code.

3. Debugging is a part of White Box Testing or Unit Testing.

4. Debugging can be performed in the development phase while conducting Unit Testing or in
phases while fixing the reported bugs.

 Testing, Quality Assurance, and Quality Control

 Most people get confused when it comes to pin down the differences among Quality
Assurance, Quality Control, and Testing.

 Although they are interrelated and to some extent, they can be considered as same
activities, but there exist distinguishing points that set them apart.

 The following table shows the difference between QA, QC, and Testing.

Quality Assurance Quality Control Testing

1. QA includes activities that It includes activities that It includes activities

ensure the implementation of ensure the verification of a that ensure the
processes, procedures and developed software with identification of
standards in context to respect to documented (or bugs/error/defects in a
verification of developed not in some cases)
 software and intended requirements. software.
requirements.

2. Focuses on processes and Focuses on actual testing Focuses on actual

procedures rather than by executing the software testing.
conducting actual testing on with an aim to identify
the system. bug/defect through
implementation of
procedures and process.

3. Process-oriented activities. Product-oriented activities. Product-oriented

activities.

4. Preventive activities. It is a corrective process. It is a preventive

process.

5. It is a subset of Software Test QC can be considered as Testing is the subset of

Life Cycle (STLC). the subset of Quality Quality Control.
Assurance.

SOFTWARE QUALITY DIMENSIONS 

Dimensions of Quality

 Accessibility: The degree to which software can be used comfortably by a wide variety

of people, including those who require assistive technologies like screen magnifiers or
voice recognition.
 Compatibility: The suitability of software for use in different environments like different
Operating Systems, Browsers, etc.
  Concurrency: The ability of software to service multiple requests to the same resources
at the same time.

 Efficiency: The ability of software to perform well or achieve a result without wasted

energy, resources, effort, time or money.

 Functionality: The ability of software to carry out the functions as specified or desired.

 Installability: The ability of software to be installed in a specified environment.

 Localizability: The ability of software to be used in different languages, time zones etc.

 Maintainability: The ease with which software can be modified (adding features,

enhancing features, fixing bugs, etc)

 Performance: The speed at which software performs under a particular load.

 Portability: The ability of software to be transferred easily from one location to another.

 Reliability: The ability of software to perform a required function under stated

conditions for the stated period of time without any errors.

 Scalability: The measure of software’s ability to increase or decrease in performance in

response to changes in software’s processing demands.

 Security: The extent of protection of software against unauthorized access, invasion of

privacy, theft, loss of data, etc.

 Testability: The ability of software to be easily tested.

 Usability: The degree of software’s ease of use.

Software Testing - ISO Standards

Many organizations around the globe develop and implement different standards to improve the
quality needs of their software. This chapter briefly describes some of the widely used standards
related to Quality Assurance and Testing.
ISO/IEC 9126

This standard deals with the following aspects to determine the quality of a software application

 Quality model

 External metrics

 Internal metrics

 Quality in use metrics

This standard presents some set of quality attributes for any software such as −

 Functionality

 Reliability

 Usability

 Efficiency

 Maintainability

 Portability

The above-mentioned quality attributes are further divided into sub-factors, which you can
study when you study the standard in detail.

ISO/IEC 9241-11

Part 11 of this standard deals with the extent to which a product can be used by specified users
to achieve specified goals with Effectiveness, Efficiency and Satisfaction in a specified context
of use.

This standard proposed a framework that describes the usability components and the
relationship between them. In this standard, the usability is considered in terms of user
performance and satisfaction. According to ISO 9241-11, usability depends on context of use
and the level of usability will change as the context changes.
ISO/IEC 25000:2005

ISO/IEC 25000:2005 is commonly known as the standard that provides the guidelines for
Software Quality Requirements and Evaluation (SQuaRE). This standard helps in organizing
and enhancing the process related to software quality requirements and their evaluations. In
reality, ISO-25000 replaces the two old ISO standards, i.e. ISO-9126 and ISO-14598.

SQuaRE is divided into sub-parts such as −

 ISO 2500n − Quality Management Division

 ISO 2501n − Quality Model Division

 ISO 2502n − Quality Measurement Division

 ISO 2503n − Quality Requirements Division

 ISO 2504n − Quality Evaluation Division

The main contents of SQuaRE are −

 Terms and definitions

 Reference Models

 General guide

 Individual division guides

 Standard related to Requirement Engineering (i.e. specification, planning, measurement

and evaluation process)

 software which are collectively known as test

Software Testing - Myths

Myth 1: Testing is Too Expensive

Reality − There is a saying, pay less for testing during software development or pay more for
maintenance or correction later. Early testing saves both time and cost in many aspects,
however reducing the cost without testing may result in improper design of a software
application rendering the product useless.

Myth 2: Testing is Time-Consuming

Reality − During the SDLC phases, testing is never a time-consuming process. However
diagnosing and fixing the errors identified during proper testing is a time-consuming but
productive activity.

Myth 3: Only Fully Developed Products are Tested

Reality − No doubt, testing depends on the source code but reviewing requirements and
developing test cases is independent from the developed code. However iterative or incremental
approach as a development life cycle model may reduce the dependency of testing on the fully
developed software.

Myth 4: Complete Testing is Possible

Reality − It becomes an issue when a client or tester thinks that complete testing is possible. It
is possible that all paths have been tested by the team but occurrence of complete testing is
never possible. There might be some scenarios that are never executed by the test team or the
client during the software development life cycle and may be executed once the project has
been deployed.

Myth 5: A Tested Software is Bug-Free

Reality − This is a very common myth that the clients, project managers, and the management
team believes in. No one can claim with absolute certainty that a software application is 100%
bug-free even if a tester with superb testing skills has tested the application.

Myth 6: Missed Defects are due to Testers

Reality − It is not a correct approach to blame testers for bugs that remain in the application
even after testing has been performed. This myth relates to Time, Cost, and Requirements
changing Constraints. However the test strategy may also result in bugs being missed by the
testing team.

Myth 7: Testers are Responsible for Quality of Product

Reality − It is a very common misinterpretation that only testers or the testing team should be
responsible for product quality. Testers’ responsibilities include the identification of bugs to the
stakeholders and then it is their decision whether they will fix the bug or release the software.
Releasing the software at the time puts more pressure on the testers, as they will be blamed for
any error.

Myth 8: Test Automation should be used wherever possible to Reduce Time

Reality − Yes, it is true that Test Automation reduces the testing time, but it is not possible to
start test automation at any time during software development. Test automaton should be started
when the software has been manually tested and is stable to some extent. Moreover, test
automation can never be used if requirements keep changing.

Myth 9: Anyone can Test a Software Application

Reality − People outside the IT industry think and even believe that anyone can test a software
and testing is not a creative job. However testers know very well that this is a myth. Thinking
alternative scenarios, try to crash a software with the intent to explore potential bugs is not
possible for the person who developed it.

Myth 10: A Tester's only Task is to Find Bugs

Reality − Finding bugs in a software is the task of the testers, but at the same time, they are
domain experts of the particular software. Developers are only responsible for the specific
component or area that is assigned to them but testers understand the overall workings of the
software, what the dependencies are, and the impacts of one module on another module.
Audit and Inspection

Audit –

It is a systematic process to determine how the actual testing process is conducted within an
organization or a team.

It is an independent examination of processes involved during the testing of a software.

As per IEEE, it is a review of documented processes that organizations implement and follow.

Types of audit include Legal Compliance Audit, Internal Audit, and System Audit.

Inspection –

It is a formal technique that involves formal or informal technical reviews of any artifact by
identifying any error or gap.

As per IEEE94, inspection is a formal evaluation technique in which software requirements,

designs, or codes are examined in detail by a person or a group other than the author to detect
faults, violations of development standards, and other problems.

Formal inspection meetings may include the following processes: Planning, Overview
Preparation, Inspection Meeting, Rework, and Follow-up.