diff --git a/courses/qa/basics-of-testing/week3/preparation.md b/courses/qa/basics-of-testing/week3/preparation.md index f514351d..86930a7e 100644 --- a/courses/qa/basics-of-testing/week3/preparation.md +++ b/courses/qa/basics-of-testing/week3/preparation.md @@ -2,16 +2,7 @@ ## Reading List -> [!TIP] -> If you have some great external resources, you might want to create an external reading list for trainees to go through before the session. +Read through this list of content before you come to the session: -Read/watch through this list of content before you come to the session: - -- [`Title`](https://example.com/) by `Author` - -## `Topic` - -> [!TIP] -> Additionally, or instead of, you may wish to write your own pre-reading content. Be sure to keep it clear, consice, related to the learning goals - and think about using images and diagrams to make it easier to digest. - -`Content goes here...` +- [`Defect Life Cycle`](https://www.softwaretestinghelp.com/bug-life-cycle/) +- [`About JIRA`](https://www.udemy.com/topic/jira/free/) diff --git a/courses/qa/basics-of-testing/week3/session-plan.md b/courses/qa/basics-of-testing/week3/session-plan.md index c189c0eb..a950e47c 100644 --- a/courses/qa/basics-of-testing/week3/session-plan.md +++ b/courses/qa/basics-of-testing/week3/session-plan.md @@ -1,28 +1,20 @@ # Session Plan -> [!TIP] -> The session plan is written to guide the mentor to prepare and run the session. Of course, trainees may come across and read this material. But it should be written as if you're speaking to a mentor. +- Welcome & Session Overview (10 minutes) + - Brief introduction to QA and defect management +- Defect vs Bug (25 minutes) + - Concept Explanation (15 minutes) + - Activity (10 minutes) +- Defect Life Cycle & Statuses (45 minutes) + - Concept Explanation (25 minutes) + - Activity (20 minutes) +- Severity vs Priority (30 minutes) + - Concept Explanation (20 minutes) + - Activity (10 minutes) +- Writing Clear & Reproducible Bug Reports (40 minutes) +- Introduction to JIRA (35 minutes) +- Wrap-up + Q&A (15 minutes) ## Session Materials -> [!TIP] -> Previously used slides, docs or any other materials that future mentors could get value from should be listed here. If we don't have any (yet), this section can be removed. - -These are some examples of previously created materials by mentors that you can use yourself, or for inspiration. - -- [`Resource Name`, `@author`, `Team X`](https://example.com/) - -## Session Outline - -> [!TIP] -> Write a plan for the order of topics, points to cover, examples, timings, exercises and any other useful info to guide the session. - -## Exercises - -> [!TIP] -> Exercises might appear inside the Session Outline section if they are tightly integrated into the flow of the session. If you have more like a library of exercises that should be worked through in order, then you could also list them in a separate section here. - -## Optional Exercises - -> [!TIP] -> If you have some extra exercises that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. +In this session, we will learn how defects are managed throughout their life cycle and how to report them effectively. We will cover the difference between a defect and a bug, explore defect statuses, and understand severity vs priority. This week also introduces best practices for writing clear, reproducible bug reports and provides hands-on experience with JIRA.