Software Testing Standards, Test Management and Test Case Development

This assignment delves into software testing standards, specifically focusing on the ISO/IEC 29119 standard. It explores the concept, definition, test processes, test documentation, and test techniques outlined in the standard. The assignment also includes practical application through the development of test cases using TestRail, covering various scenarios such as syntax error identification, element verification, and search item validation. A bug report example is provided, highlighting the advantages of software testing and the role of TestRail in the software development life cycle. The student's work showcases practical test case creation and analysis, along with a discussion on the importance of software testing standards for producing bug-free and secure software products. The assignment also references relevant literature to support its claims, providing a comprehensive overview of software testing practices.

Running head: SOFTWARE TESTING STANDARDS
1
Software Testing Standards
Name
University
Date:

SOFTWARE TESTING STANDARDS
2
Part A: ISO/IEC 29119
Concept and Definition
Software testing is a fundamental stage in the process of developing a product. The
ISO/IEC 29119 is a software standard released in 2013, which defines the documentation,
vocabulary, process, and techniques within a software development cycle (García, Meléndez, &
Dávila, 2018). Software testing processes have from a general phase of debugging to one that
considers bug-free products with mismatched logic and product improvement. Some of the
modern trends found in the ISO/IEC 29119 include the agile and mobile testing, automation
testing, test factories, and the context-driven testing . One of the reason for the standardization of
software testing techniques is to enable the universal usage, especially for small companies and
organizations that do not have the means to develop internal testing equipment. The
standardization enables them to employ workers who are already familiar with the processes,
thus enabling quicker and cheaper software development and life cycle management.
Test Processes
A process model is a framework of activities, processes, ad artifacts that enable proper
communication and collaboration of product testing (Eira, et al., 2016). An organization or
company’s rate of maturity in the development of software products is measured by the level of
implementation of the ISO/IEC 29119 framework in its day-to-day operations. In the second
standard part of the ISO/IEC 29119 model relates to the generic processes that are part of the
software development cycle. It can be applied to organizations of any kind of product or size.
Numerous standards have been defined in this model. Therefore, a project manager chooses the
parts that are applicable to the different sections. The described approach is referred to as the
adapted compliance. The alternative is fully implement all standards in a process model called

SOFTWARE TESTING STANDARDS
3
the full compliance counterpart. The ISO/IEC 29119 has 8 processes split into 89 base practices
and 50 artifacts (Ali & Yue, 2015). Its levels are divided into five based on their capabilities:
Managed, Performed, Predictable, Established, and Innovating. The ISO/IEC 29119 may be seen
as a continuous process model with two major classifications: architectural, and assessment
based.
Test Documentation
The test documentation is defined under the ISO/IEC 29119-3:2013, which was
published in the year 2013. It includes the definition of test templates and test documentation
examples that are internationally accepted (Kasurinen, 2010). The organization of the documents
reflects the overall test process in accordance with the process adaptation defined by the test
processes phase (section 2 i.e. ISO/IEC 29119-2). The documentation phase contains annexes A,
B, C, D to S, and T. A contains the document contents, B shows the mappings of ISO/IEC 29119
section 2. C provides an example-based approach, while D-S have template application case
examples. Annex T maps the standards to the currently applied standards. The crucial purpose of
the documentation section is to provide a dynamic testing mechanism that is functional for both
automated and manual testing procedures, whether scripted or unscripted.
Test Techniques
The software testing techniques are defined under the ISO/IEC 29119-4 standard, which
provides the standard test methods and their sample implementations. The project administrator
decides the level of applicability of the testing techniques to present or planned projects within
the company (ISO Software and systems engineering, 2013). Three kinds of techniques are
defined: Specification-based, structure-based, and the experienced based models. They entail an
array of methods that enable a team of testing professionals to determine the stability of a

SOFTWARE TESTING STANDARDS
4
product in different areas of application, in whatever conditions, and the potential for
improvement (Software Testing Standards Org., 2018).
Conclusion
Testing standards have become a crucial part of the modern software development life
cycle. They enable companies to subject their products to various extreme conditions or
functions that normal and advanced users may attempt to accomplish. The ISO/IEC/IEEE 29119
modern testing standards companies from having to recall products and enables the creation of a
roadmap for product improvement.
Test Cases
Note: TestRail work to be completed by the student.
Project Name:
Module name:
Created by:
Date of Creation:
Reviewed by:
Date of Review:
Test scenario
Test
Scenario
ID
Test
Scenario
Description
Test
Case
ID
Test Case
Description
Test
Case
Type
Expected
Result
Act
ual
Res
ult
Status
1 Syntax error
identification
1 Paste the code
into Testrail
IDE window
And declare
the array
values
Positive Error thrown
in console
2 Syntax error
identification
2 Paste the code
into Testrail
Negative Code runs
successfully.

SOFTWARE TESTING STANDARDS
5
IDE window
3 Verification
of element
on left hand
side
3 Enter array
with search
item on the left
half of the
array
Positive Midvalue+1
4 Verification
of element
on left hand
side
4 Enter array
with search
item on the left
half of the
array
Negative Midvalue-1
5 Verification
of element
on right hand
side of an
array
5 Enter array
with search
item on the
right half of
the array
Positive Midvalue-1
6 Verification
of element
on right hand
side of an
array
6 Enter array
with search
item on the
right half of
the array
Negative Midvalue+1
7 Item to
search equals
midvalue
7 Set search
item to equal
the mid value
of the array
Positive Midvalue
8 Item to
search equals
midvalue
8 Set search
item to equal
the mid value
of the array
Negative Midvalue-1,
midvalue+1
9 Search item
absence
9 Set search
item to a
number that is
not within the
array
Negative -1
10 Search item
absence
10 Set search
item to a
number that is
not within the
array
Positive Midvalue-1
11 More than
one search
item on both
left and right
hand sides
11 Enter an array
with a
duplicated
number on
both sides of
the array
Positive Midvalue-1
12 More than 12 Send Positive highest index

SOFTWARE TESTING STANDARDS
6
one search
item on same
side.
information
into database
tables
position of the
search
element
Bug Report
A software may contain bugs. For instance, with reference to the user verification login,
the software may approve an individual who uses the email in the username and password fields.
This bug can be identified as a negative test that is to be rectified. The logic of the program could
be re-written to eliminate such kinds of scenarios. All positive test cases should return a
‘positive’ result while negative ones should return ‘negative’ outcomes.
Advantages of Software Testing
1. Software testing standards enable companies to produce software that is bug-free.
2. The testing phase provides a chance for the company to find out new features to be added
during the SDLC iteration.
3. The test cases provides helps to increase the security of an application through the
validation of login credentials and other crucial access details.
Conclusion
Test Rail is an important tool in the process of software development. The tool can help
software engineers and programmers achieve better results with regards to elimination of logical
bugs. It can also help to identify areas that can be developed further to enable the creation of a
better product in the software development life cycle.

SOFTWARE TESTING STANDARDS
7
References
Ali, S., & Yue, T. (2015). Formalizing the ISO/IEC/IEEE 29119 Software Testing Standard.
2015 ACM/IEEE 18th International Conference on Model Driven Engineering
Languages and Systems (MODELS), (pp. 396–405). doi:IEEE.
https://doi.org/10.1109/MODELS.2015.7338271
Eira, P., Guimaraes, P., Melo, M., Brito, M. A., Silva, A., & Machado, R. J. (2016). Adoption of
ISO/IEC 29119-2 software testing practices: An exploratory analysis in organizations in
Lima, Perú. 2016 International Conference on Software Process Improvement (CIMPS)
(pp. 1-8). CIMPS. doi:https://doi.org/10.1109/CIMPS.2016.7802802
García, C., Meléndez, K., & Dávila, A. (2018, February 8). Adoptability of Test Process Models:
ISO/IEC 29119, TMMI y TPI from the small organization perspective. Retrieved from
http://recibe.cucei.udg.mx/revista/vol7-no1/computacion03.pdf
ISO Software and systems engineering. (2013). SOFTWARE AND SYSTEMS ENGINEERING --
SOFTWARE TESTING -- PART 3: TEST DOCUMENTATION. ISO Software and
systems engineering.
Kasurinen, J. (2010). Elaborating Software Test Processes and Strategies. 2010 Third
International Conference on Software Testing, Verification and Validation (pp. 355–
358). IEEE. doi:https://doi.org/10.1109/ICST.2010.25
Software Testing Standards Org. (2018, December 11). ISO/IEC/IEEE 29119-4: Test
Techniques. Retrieved from https://softwaretestingstandard.org/part4.php