SDLC (Software Development Life Cycle) is the structured process followed to develop software, covering stages like planning, analysis, design, development, testing, deployment, and maintenance.
STLC (Software Testing Life Cycle) is a subset of SDLC that focuses specifically on testing, including phases like requirement analysis, test planning, test case development, environment setup, test execution, and closure.
While SDLC ensures the creation of functional software, STLC ensures its quality and reliability.
Both cycles work together to deliver high-quality software efficiently.

Testing principles guide effective software testing—key ones include: testing shows defects, early testing saves time, exhaustive testing is impossible, and defect clustering.

Types of testing include:

• Functional testing (e.g., unit, integration, system)

• Non-functional testing (e.g., performance, security, usability)

• Manual and automation testing

Testing techniques are:

• Black-box (testing without internal knowledge)

• White-box (testing internal logic and code)

• Grey-box (a mix of both)

Together, these ensure comprehensive and efficient test coverage

Requirement analysis is the process of understanding what the software should do by reviewing business needs, specifications, and user expectations. Testers identify testable requirements and potential gaps or ambiguities early on.

Test case writing involves creating detailed steps to verify each requirement, including inputs, expected outputs, and conditions. Well-written test cases are clear, reusable, and traceable to requirements, ensuring thorough and systematic testing of the application.

The bug life cycle represents the stages a defect goes through from identification to closure. Key stages include:

1. New – Bug is reported.

2. Assigned – Developer is assigned to fix it.

3. Open/In Progress – Work on the bug begins.

4. Fixed – Developer resolves the issue.

5. Tested/Verified – Tester retests the fix.

6. Closed – Bug is confirmed resolved.

7. Reopened – If the issue still exists after testing.

In Jira, defects are logged as issues with details like severity, steps to reproduce, and screenshots. Jira allows tracking bug status, assigning tasks, setting priorities, adding comments, and integrating with development tools, enabling efficient defect management and collaboration.

Test Plan and Test Strategy are key documents in the software testing process:

• Test Plan is a detailed document outlining the scope, objectives, resources, schedule, test environment, deliverables, and risk management for a specific project. It answers “what to test, how, when, and who will do it.”

• Test Strategy is a high-level organizational document that defines the overall testing approach across projects. It covers test levels, types, tools, standards, and responsibilities. It answers “how testing will be carried out across the organization.”

Together, they ensure clear direction, consistent practices, and effective quality assurance.