1.

Name of Course/Module: Software Testing

2. Course Code: CST401
3. Rationale for the inclusion of the course/module in the programme:

Software testing is one of the fundamental areas to ensure a particular software meets its
expected goals and requirements. This is an important course that enables students to acquire
the necessary skills to perform software testing that covers a wide range of concepts including
the techniques, strategies, processes, analysis and others.

4. Semester and Year offered: Semester 5 Year 3

5. Credit Value: 3
6. Prerequisite (if any): None
7. Objectives:
The objectives of this course are to:
 Explain an introduction to the software engineering testing process;
 Analyze requirements to determine appropriate testing strategies;
 Design and construct comprehensive test plans;
 Apply various testing techniques, methods, and tools effectively and efficiently;
 Estimate test coverage and yield according to a variety of criteria;
 Use statistical techniques to evaluate the defect density and the likelihood of faults;
 Prepare reviews and inspections; and
 Manage a software project to fulfill customer requirements.
 Explain managerial and entrepreneurial skills relevant to software testing.
8. Learning outcomes:
Upon completion, the students should be able to:
 Apply the concept of software testing to facilitate software development.
 Identify the current technology trends in software testing.
 Construct and develop information system that is of high quality and consistent with
business goals of an organization by applying state of the art software testing techniques.
 Complete projects on software testing by applying managerial skills in formulating project
plan and entrepreneurial skills in drawing effective project execution.
9. Transferable Skills:
Analytical – Students will be taught how to evaluate various performance metrics of
software testing to justify whether the software meets the requirements, and make the right
choice of decision.

Testing – Students will be taught how to perform tests including developing test plans and
determining the right choice of testing process and strategy.

Applying mathematics – Students will be taught to calculate performance metrics, and use
statistical techniques to evaluate test results.

Management – Students will be taught to manage test process.

Project - Students will be given exposure working on a project which can be on an

individual or team basis.
10. Teaching-learning and assessment strategy:
Teaching-learning
 Lectures - Lectures are conducted weekly that cover every topic stated in the course
outline. Lecturers also promote interactive learning with the students where mutual
participation in question and answer and short discussion are expected.
 Tutorials - Students will be given assignment consisting short questions that require
investigation and to be answered.

Assessment
 Exam – it is a written form of summative assessment which is conducted in the final
exam.
 Quiz - It is a written form of formative assessment that may be conducted during the
lecture period.
 Assignment - It is a take home task that student has to complete outside of the
classroom. It can be in the form of practical or theoretical report.
 Project - It is a take home task that student has to complete outside of the classroom. It
may be assigned to an individual or group where marks are given based on the
fulfillment to the assessment criteria of the project.
 Presentation - Student is assessed on the communication skills.

11. Synopsis:
This course covers the testing process used to assess the quality of computer software. Software
testing is an empirical technical investigation conducted to provide stakeholders with information
about the quality of the product or service under test, with respect to the context in which it is
intended to operate. This course includes, but is not limited to, the process of executing a
program or application with the intent of finding software bugs, advanced topics on software
testing with deep exposure to various testing strategies and techniques such as testing process,
pre-release testing, post release testing, regression testing, finding faults early, measuring
software testing, testing artifacts, sample testing cycle; the management of the testing process
and the economics of software testing will be covered as well.

12. Mode of Delivery

Lectures and Tutorials
13. Assessment Methods and Types
Continuous assessment: 60%
Final exam: 40%
14. Mapping of the course/module to the Programme Aims
 Competent information and communication technology practitioner with solid theoretical
and practical knowledge in the area of information technology.
 IT professional who is a proficient in communicating the state-of-the-art in information
technology.
 IT professional who has the abilities in leading the specific task in a team with qualities
in decision making and entrepreneurial attributes.
15. Mapping of the course/module to the Programme Learning Outcomes
 Able to apply knowledge and skills in the field of information and communication
technology management.
 Able to solve real world problem using information and communication technology
approach and techniques.
 Able to express ideas and opinions effectively in various communication style, tools and
media.
 Able to recognize and formulate new approach or method in providing IT technical
solutions.
 Able to deliver and produce ideas and solutions with entrepreneurial and technical
solutions.
 Able to be participate in a project-based assignment at individual or team level.

16. Content outline of the course/module and the SLT per topic

Topics

1. INTRODUCTION TO TESTING :AS AN

ENGINEERING A C T I V I T Y
1.0 The Evolving Profession of Software Engineering
1.1 The Role of Process in Software Quality
1.2 Testing as a Process
1.3 Overview of the Testing Maturity Model (TMM)
1.3.1 TMM Levels

2. Software Testing Fundamentals, Testing Techniques

and Principles
2.1. Defects vs Failures
2.2. Equivalence Classes
2.3. Boundary Testing
2.4. Types of Defects
 Black-box vs Structural Testing

3. DEFECTS, HYPOTHESES, AND TESTS

3.0 Origins of Defects
3.1 Defect Classes, the Defect Repository, and Test
Design
3.1.1 Requirements and Specification Defects
3.1.2 Design Defects
3.1.3 Coding Defects
3.1.4 Testing Defects
3.2 Defect Examples: The Coin Problem
3.3 Developer/Tester Support for Developing a Defect
Repository

4. Testing Strategies-I
4.1. Unit testing
4.2. Integration Testing
4.3. Profiling
4.4. Test Driven Development
4.5. State Based Testing
4.6. Configuration Testing
4.7. Compatibility Testing
4.8. Web Site Testing
4.9. Alpha, Beta and Acceptance Testing
5. STRATEGIES AND METHODS FOR TEST CASE
DESIGN II
5.0 Using the White Box Approach to Test Design
5.1 Test Adequacy Criteria
5.2 Coverage and Control Flow Graphs
5.3 Covering Code Logic
5.4 Paths: Their Role in White Box–Based Test Design
5.5 Additional White Box Test Design Approaches
5.5.1 Data Flow and White Box Test Design
5.5.2 Loop Testing
5.5.3 Mutation Testing
5.6 Evaluating Test Adequacy Criteria
5.7 White Box Testing Methods and the TMM

6. LEVELS OF TESTING
6.0 The Need for Levels of Testing
6.0.1 Levels of Testing and Software Development
Paradigms
6.1 Unit Test: Functions, Procedures, Classes, and
Methods as Units
6.2 Unit Test: The Need for Preparation
6.3 Unit Test Planning
6.4 Designing the Unit Tests
6.5 The Class as a Testable Unit: Special
Considerations
6.6 The Test Harness
6.7 Running the Unit Tests and Recording Results
6.8 Integration Test: Goals
6.9 Integration Strategies for Procedures and
Functions
6.10 Integration Strategies for Classes
6.11 Designing Integration Tests
6.12 Integration Test Planning
6.13 System Test: The Different Types
6.13.1 Functional Testing
6.13.2 Performance Testing
6.13.3 Stress Testing
6.13.4 Configuration Testing
6.13.5 Security Testing
6.13.6 Recovery Testing
6.14 Regression Testing
6.15 Alpha, Beta, and Acceptance Tests
6.16 Summary Statement on Testing Levels
6.17 The Special Role of Use Cases
6.18 Levels of Testing and the TMM
 7. TEST GOALS, P O L I C I E S , PLANS, AND
DOCUMENTATION
7.0 Introductory Concepts
7.1 Testing and Debugging Goals and Policies
7.2 Test Planning
7.3 Test Plan Components
7.4 Test Plan Attachments
7.4.1 Test Design Specifications
7.4.2 Test Case Specifications
7.4.3 Test Procedure Specifications
7.5 Locating Test Items: The Test Transmittal Report
7.6 Reporting Test Results
7.7 The Role of the Three Critical Groups in Test
Planning and Policy Development
7.8 Process and the Engineering Disciplines: The Role
of the Individual as a Process Facilitator
8. Testing Process
8.1. Pre-release testing
8.2. Post release testing
8.3. Regression testing
8.4. Finding faults early
8.5. Measuring software testing
8.6. Testing artifacts- A sample testing cycle
9. Coverage Criteria
 Test Instrumentation and Tools
 Developing Test Plans
 Managing the Testing Process
 Problem, Reporting, Tracking and Analysis
17.Main references supporting the course:
Naik, K., & Tripathy, P. (2008). Software testing and quality assurance: theory and
practice. John Wiley and Sons.

Additional references supporting the course

Ammann, P., & Offutt, J. (2008). Introduction to software testing. Cambridge University Press.

Hass, A. M. J. (2008). Guide to advanced software testing. Artech House.

18. Other additional information

None