Index

SR. NO. DATE PRACTICAL NUMBER TOPIC PAGE NO. SIGN
1. 22-01-2025 1 Introduction to Software Testing 02
2. 05-02-2025 2 Reliability Testing 04
3. 13-02-2025 3 Expectation & Functional Error Report - Severity & Priority 11
4. 17-02-2025 4 Static Testing
• SRS Review & Inspection 18
5. 21-02-2025 5 Test Automation Tools
• Agile Management:Taiga
• Load Testing:JMeter
• Mobile-App Testing:FireBase
• Test Management Tool:Azure 22
6. 07-03-2025 5(A) Automation Testing using Selenium
• IDE
• WebDrivers
• Test NG 41
7. 12-03-2025 6 Dynamic Testing
• Black Box Testing 48
8. 19-03-2025 6 (A) Boundary Value Analysis (BVA) 50
9. 26-03-2025 6 (B) Equivalence Partitioning (EP) 55
10. 02-04-2025 6(C) Decision Table Testing 57
11. 09-04-2025 6(D) Cause-Effect Graphing 60
12. 09-04-2025 6(E) State Transition 62
13. 09-04-2025 6(F) Use-Case Testing 66
14. 16-04-2025 7 White Box Testing 73
15 17-04-2025 7(A) Past Testing:(Cyclomatic complexity)
16 23-04-25 8 Website testing

Session 1 (Introduction to Software Testing)

  1. Aim

    1. The aim of "Introduction to Software Testing" is to provide foundational knowledge of software testing principles, techniques, and tools. It focuses on ensuring software quality through systematic test planning, execution, and defect detection, helping identify and resolve issues before deployment

  2. Problem Statement:

    1. This assignment introduces software testing, emphasizing its importance in delivering quality software. It focuses on identifying errors, defects, and failures in software systems to ensure reliability and efficiency

  3. Theory:

    1. Definition - Software testing is the process of evaluating software to ensure it meets the specified requirements and identifies defects.
    2. Purpose - To detect and correct errors, ensuring software reliability and performance.
    3. Methods - Testing can be manual or automated and includes different testing levels (unit, integration, system, and acceptance testing).
    4. Types of Faults - Algorithmic, computation, documentation, stress, capacity, timing, and recovery faults.
    5. Software Bugs - Caused by unclear requirements, poor documentation, coding mistakes, and communication gaps.

  4. Observations:

    1. Software testing helps in finding errors before deployment.
    2. Faults in software can be due to human mistakes (errors) or defects in code.
    3. Different testing techniques such as functional, integration, and system testing help identify bugs.
    4. A well-tested software product ensures better user satisfaction and lower maintenance costs.
    5. Failures occur when faults in the software are executed, leading to incorrect results

  5. Conclusion:

    1. The introduction to software testing was successfully implemented.
    2. Software testing ensures quality and reliability in software applications.
    3. Identifying and fixing defects early in the development process reduces costs and enhances performance.
    4. Different testing techniques play a crucial role in detecting software issues.
    5. A well-tested software product meets user expectations and business requirements.