Scribd
Upload
30 views2 pages

Software Testing Course Syllabus

Complete syllabus for Software Testing BCA

Uploaded by

hadakanishka09
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
30 views2 pages

Software Testing Course Syllabus

Complete syllabus for Software Testing BCA

Uploaded by

hadakanishka09
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

3. M.H.

Dunham, “Data Mining: Introductory and Advanced Topics”, Pearson


Education 2006.

Course Name: Software Testing


Course Code: BCA176A

L (Hr.) T (Hr.) Pr (Hr.) Credits


3 0 0 3

Course Objective:
1. To apply the testing strategies and methodologies in their projects
2. To understand test management strategies and tools for testing
3. A keen awareness on the open problems in software testing and maintenance

UNIT-I TESTING BASICS


Testing as an engineering activity – Role of process in software quality – Testing as a process
– Basic definitions – Software testing principles – The tester’s role in a software development
organization – Origins of defects – Defect classes – The defect repository and test design –
Defect examples – Developer / Tester support for developing a defect repository.

UNIT-II TEST CASE DESIGN


Introduction to testing design strategies – The smarter tester – Test case design strategies –
Using black box approach to test case design – Random testing – Equivalence class
partitioning – Boundary value analysis – Other black box test design approaches – Black box
testing and COTS – Using white box approach to test design – Test adequacy criteria –
Coverage and control flow graphs –Covering code logic – Paths – Their role in white box
based test design –Additional white box test design approaches – Evaluating test adequacy
criteria.

UNIT-III LEVELS OF TESTING

189 | School of Computer Applications, JECRC University, Jaipur


The need for levels of testing – Unit test – Unit test planning – Designing the unit tests – The
class as a testable unit – The test harness – Running the unit tests and recording results –
Integration tests – Designing integration tests – Integration test planning – System test – The
different types – Regression testing – Alpha,beta and acceptance tests.

UNIT-IV TEST MANAGEMENT


Basic concepts – Testing, debugging goals, policies – Test planning – Test plan
components – Test plan attachments – Locating test items – Reporting test
results – The role of three groups in test planning and policy development –
Process and the engineering disciplines – Introducing the test specialist – Skills needed by a
test specialist – Building a testing group.
CONTROLLING AND MONITORING
Defining terms – Measurements and milestones for controlling and monitoring –
Status meetings – Reports and control issues – Criteria for test completion – SCM – Types of
reviews – Developing a review program – Components of review plans – Reporting review
results.
UNIT-V SOFTWARE QUALITY ASSURANCE
Quality Concepts , Quality , Quality Control , Quality Assurance , Cost of Quality , The
Quality Movement ,Software Quality Assurance , Background Issues , SQA Activities
,Software Reviews , Cost Impact of Software Defects , Defect Amplification and Removal ,
Formal Technical Reviews , The Review Meeting , Review Reporting and Record Keeping ,
Review Guidelines , Formal Approaches to SQA , Statistical Software Quality Assurance ,
Software Reliability , Measures of Reliability and Availability, Software Safety , Mistake-
Proofing for Software , The ISO 9000 Quality Standards , The ISO Approach to Quality
Assurance Systems The ISO 9001 Standard ,The SQA Plan ,

Text Books
1. SrinivasanDesikan, Gopalaswamy Ramesh, “Software Testing: Principles and Practices”,
Pearson 2012
2. Aditya P. Mathur, “Foundations of Software Testing”, Pearson, 2008

References:
1. Paul Ammann, Jeff Offutt, “Introduction to Software Testing”, Cambridge University
Press, 2008
2. Paul C. Jorgensen, “Software Testing: A Craftsman's Approach”, Auerbach Publications,
2008

Upon completion of this subject, the student will be able to:

Course Outcome(CO)
1. The students learn testing and how apply the testing strategies and methodologies in their
projects
2. Use concepts of test management strategies and tools for testing
3. A keen awareness on the open problems in software testing and maintenance.

190 | School of Computer Applications, JECRC University, Jaipur

Common questions

Powered by AI

Black box testing approaches test case design strategies by focusing on inputs and outputs without regard to the internal code structure, involving methods like equivalence class partitioning and boundary value analysis. In contrast, white box testing involves understanding the internal workings of the code, using coverage and control flow graphs, and ensuring paths are adequately tested in test design .

The main levels of testing include unit testing, integration testing, system testing, and regression testing. Unit testing focuses on individual components or classes, integration testing examines the interactions between integrated units, system testing evaluates the complete system, and regression testing ensures that new changes do not adversely affect existing functionalities. These levels are interrelated, as each builds on the findings and assurances of the preceding level .

The key principles of software testing include understanding testing as an engineering activity, recognizing the role of process in software quality, and viewing testing as a process itself. Additionally, it covers the tester's role in a software development organization, identifying the origins and classes of defects, and the importance of a defect repository in test design .

Formal technical reviews play a critical role in enhancing software quality by systematically examining software artifacts and identifying defects early in the development process. These reviews promote accountability, facilitate knowledge sharing, and reduce rework by ensuring adherence to standards and identifying potential risks, thereby significantly reducing defects and improving the overall quality of the software product .

Open problems in software testing and maintenance include handling complex system interactions, ensuring comprehensive test coverage, adapting to rapidly changing technologies, and managing resource constraints. Continuous improvement in test design strategies and test management practices is necessary to address these challenges and maintain software quality in dynamic development environments .

Developing and utilizing a defect repository involves identifying and categorizing defect classes, collecting defect examples, and utilizing these in test design to improve software quality. Developers and testers collaborate to build a comprehensive repository that aids in foreseeing potential defects and designing effective test cases, facilitating better defect tracking and resolution .

Essential skills for a test specialist include knowledge of testing methodologies, analytical thinking, effective communication, proficiency in using testing tools and techniques, and the ability to collaborate with development teams. These skills are vital for developing effective test cases, identifying potential defects, and ensuring thorough testing of software projects .

Test planning and test management are critical for setting clear goals, establishing responsibilities, and defining policies and procedures for software testing. They involve creating detailed test plans, assigning tasks to testing specialists, and managing resources to ensure comprehensive coverage and timely completion of testing phases. These activities help in identifying test items, determining completion criteria, and reporting test results, thereby contributing to effective software testing .

Statistical Software Quality Assurance (SQA) utilizes data-driven techniques to assess software processes and predict potential defects, enhancing the reliability and safety of software. By applying statistical methods, SQA can identify trends, control the quality, and ensure that safety measures are consistently adhered to, thus improving the overall trustworthiness of the software .

Defect amplification refers to the tendency of defects to multiply and impact multiple parts of the system as software development progresses. Early defect removal through thorough testing can prevent this proliferation and minimize the cost impact of software defects. Effective defect management, including rigorous testing and formal reviews, is crucial to minimize defect amplification and enhance software quality .

You might also like