diff --git a/courses/qa/README.md b/courses/qa/README.md new file mode 100644 index 00000000..b1a674ba --- /dev/null +++ b/courses/qa/README.md @@ -0,0 +1,14 @@ +# Quality Assurance + +Our QA Tech Track offers a comprehensive 12-week training program designed to equip aspiring quality assurance professionals with both practical skills and industry-aligned knowledge. + +## Modules + +| Name | Weeks | +| ------------------------------------------------------------ | ----- | +| [Basics Of Testing](/courses/qa/basics-of-testing/README.md) | 5 | +| [Test Automation](/courses/qa/test-automation/README.md) | 5 | +| [Test Management](/courses/qa/test-management/README.md) | 4 | +| [Career Training](/courses/qa/career-training/README.md) | 1 | + +Total: 15 weeks diff --git a/courses/qa/basics-of-testing/README.md b/courses/qa/basics-of-testing/README.md new file mode 100644 index 00000000..50da33de --- /dev/null +++ b/courses/qa/basics-of-testing/README.md @@ -0,0 +1,27 @@ +# `Module Name` + +This module is about `description goes here` + +## Contents + +| Week | Topic | Preparation | Session Plan | Assignment | +| ---- | ------------------------------------ | ------------------------------------- | ----------------------------------------------------- | ----------------------------------- | +| 1. | [`Session Title`](./week1/README.md) | [Preparation](./week1/preparation.md) | [Session Plan](./week1/session-plan.md) (for mentors) | [Assignment](./week1/assignment.md) | + +## Module Learning Goals + +> [!TIP] +> Learning goals should be a list of outcomes, rather than a list of topics. For example, instead of "Synchronous vs Asynchronous", write something like "Explain the difference between sync and async code execution in JavaScript" + +By the end of this module, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` + +## Prerequisites + +> [!TIP] +> Some modules build on the learning goals of other modules. If that is the case, link them below. If there are no prerequesites, feel free to remove this section. Note that it is assumed that all foundation modules are a prerequisite of a specialisation course and its modules, so in that case you don't have to write them all out here :-) + +You should have completed or understand the learning goals in the following modules before proceeding: + +- [`Module Name`](https://example.com) diff --git a/courses/qa/basics-of-testing/week1/README.md b/courses/qa/basics-of-testing/week1/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/basics-of-testing/week1/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/basics-of-testing/week1/assignment.md b/courses/qa/basics-of-testing/week1/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/basics-of-testing/week1/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/basics-of-testing/week1/preparation.md b/courses/qa/basics-of-testing/week1/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/basics-of-testing/week1/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/basics-of-testing/week1/session-materials/example-session-material.md b/courses/qa/basics-of-testing/week1/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/basics-of-testing/week1/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/basics-of-testing/week1/session-plan.md b/courses/qa/basics-of-testing/week1/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/basics-of-testing/week1/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/basics-of-testing/week2/README.md b/courses/qa/basics-of-testing/week2/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/basics-of-testing/week2/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/basics-of-testing/week2/assignment.md b/courses/qa/basics-of-testing/week2/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/basics-of-testing/week2/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/basics-of-testing/week2/preparation.md b/courses/qa/basics-of-testing/week2/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/basics-of-testing/week2/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/basics-of-testing/week2/session-materials/example-session-material.md b/courses/qa/basics-of-testing/week2/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/basics-of-testing/week2/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/basics-of-testing/week2/session-plan.md b/courses/qa/basics-of-testing/week2/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/basics-of-testing/week2/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/basics-of-testing/week3/README.md b/courses/qa/basics-of-testing/week3/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/basics-of-testing/week3/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/basics-of-testing/week3/assignment.md b/courses/qa/basics-of-testing/week3/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/basics-of-testing/week3/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/basics-of-testing/week3/preparation.md b/courses/qa/basics-of-testing/week3/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/basics-of-testing/week3/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/basics-of-testing/week3/session-materials/example-session-material.md b/courses/qa/basics-of-testing/week3/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/basics-of-testing/week3/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/basics-of-testing/week3/session-plan.md b/courses/qa/basics-of-testing/week3/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/basics-of-testing/week3/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/basics-of-testing/week4/README.md b/courses/qa/basics-of-testing/week4/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/basics-of-testing/week4/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/basics-of-testing/week4/assignment.md b/courses/qa/basics-of-testing/week4/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/basics-of-testing/week4/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/basics-of-testing/week4/preparation.md b/courses/qa/basics-of-testing/week4/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/basics-of-testing/week4/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/basics-of-testing/week4/session-materials/example-session-material.md b/courses/qa/basics-of-testing/week4/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/basics-of-testing/week4/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/basics-of-testing/week4/session-plan.md b/courses/qa/basics-of-testing/week4/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/basics-of-testing/week4/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/career-training/README.md b/courses/qa/career-training/README.md new file mode 100644 index 00000000..50da33de --- /dev/null +++ b/courses/qa/career-training/README.md @@ -0,0 +1,27 @@ +# `Module Name` + +This module is about `description goes here` + +## Contents + +| Week | Topic | Preparation | Session Plan | Assignment | +| ---- | ------------------------------------ | ------------------------------------- | ----------------------------------------------------- | ----------------------------------- | +| 1. | [`Session Title`](./week1/README.md) | [Preparation](./week1/preparation.md) | [Session Plan](./week1/session-plan.md) (for mentors) | [Assignment](./week1/assignment.md) | + +## Module Learning Goals + +> [!TIP] +> Learning goals should be a list of outcomes, rather than a list of topics. For example, instead of "Synchronous vs Asynchronous", write something like "Explain the difference between sync and async code execution in JavaScript" + +By the end of this module, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` + +## Prerequisites + +> [!TIP] +> Some modules build on the learning goals of other modules. If that is the case, link them below. If there are no prerequesites, feel free to remove this section. Note that it is assumed that all foundation modules are a prerequisite of a specialisation course and its modules, so in that case you don't have to write them all out here :-) + +You should have completed or understand the learning goals in the following modules before proceeding: + +- [`Module Name`](https://example.com) diff --git a/courses/qa/career-training/week1/README.md b/courses/qa/career-training/week1/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/career-training/week1/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/career-training/week1/assignment.md b/courses/qa/career-training/week1/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/career-training/week1/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/career-training/week1/preparation.md b/courses/qa/career-training/week1/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/career-training/week1/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/career-training/week1/session-materials/example-session-material.md b/courses/qa/career-training/week1/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/career-training/week1/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/career-training/week1/session-plan.md b/courses/qa/career-training/week1/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/career-training/week1/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-automation/README.md b/courses/qa/test-automation/README.md new file mode 100644 index 00000000..50da33de --- /dev/null +++ b/courses/qa/test-automation/README.md @@ -0,0 +1,27 @@ +# `Module Name` + +This module is about `description goes here` + +## Contents + +| Week | Topic | Preparation | Session Plan | Assignment | +| ---- | ------------------------------------ | ------------------------------------- | ----------------------------------------------------- | ----------------------------------- | +| 1. | [`Session Title`](./week1/README.md) | [Preparation](./week1/preparation.md) | [Session Plan](./week1/session-plan.md) (for mentors) | [Assignment](./week1/assignment.md) | + +## Module Learning Goals + +> [!TIP] +> Learning goals should be a list of outcomes, rather than a list of topics. For example, instead of "Synchronous vs Asynchronous", write something like "Explain the difference between sync and async code execution in JavaScript" + +By the end of this module, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` + +## Prerequisites + +> [!TIP] +> Some modules build on the learning goals of other modules. If that is the case, link them below. If there are no prerequesites, feel free to remove this section. Note that it is assumed that all foundation modules are a prerequisite of a specialisation course and its modules, so in that case you don't have to write them all out here :-) + +You should have completed or understand the learning goals in the following modules before proceeding: + +- [`Module Name`](https://example.com) diff --git a/courses/qa/test-automation/week1/README.md b/courses/qa/test-automation/week1/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-automation/week1/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-automation/week1/assignment.md b/courses/qa/test-automation/week1/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-automation/week1/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-automation/week1/preparation.md b/courses/qa/test-automation/week1/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-automation/week1/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-automation/week1/session-materials/example-session-material.md b/courses/qa/test-automation/week1/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-automation/week1/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-automation/week1/session-plan.md b/courses/qa/test-automation/week1/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-automation/week1/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-automation/week2/README.md b/courses/qa/test-automation/week2/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-automation/week2/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-automation/week2/assignment.md b/courses/qa/test-automation/week2/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-automation/week2/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-automation/week2/preparation.md b/courses/qa/test-automation/week2/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-automation/week2/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-automation/week2/session-materials/example-session-material.md b/courses/qa/test-automation/week2/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-automation/week2/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-automation/week2/session-plan.md b/courses/qa/test-automation/week2/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-automation/week2/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-automation/week3/README.md b/courses/qa/test-automation/week3/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-automation/week3/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-automation/week3/assignment.md b/courses/qa/test-automation/week3/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-automation/week3/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-automation/week3/preparation.md b/courses/qa/test-automation/week3/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-automation/week3/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-automation/week3/session-materials/example-session-material.md b/courses/qa/test-automation/week3/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-automation/week3/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-automation/week3/session-plan.md b/courses/qa/test-automation/week3/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-automation/week3/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-automation/week4/README.md b/courses/qa/test-automation/week4/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-automation/week4/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-automation/week4/assignment.md b/courses/qa/test-automation/week4/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-automation/week4/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-automation/week4/preparation.md b/courses/qa/test-automation/week4/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-automation/week4/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-automation/week4/session-materials/example-session-material.md b/courses/qa/test-automation/week4/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-automation/week4/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-automation/week4/session-plan.md b/courses/qa/test-automation/week4/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-automation/week4/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-management/README.md b/courses/qa/test-management/README.md new file mode 100644 index 00000000..50da33de --- /dev/null +++ b/courses/qa/test-management/README.md @@ -0,0 +1,27 @@ +# `Module Name` + +This module is about `description goes here` + +## Contents + +| Week | Topic | Preparation | Session Plan | Assignment | +| ---- | ------------------------------------ | ------------------------------------- | ----------------------------------------------------- | ----------------------------------- | +| 1. | [`Session Title`](./week1/README.md) | [Preparation](./week1/preparation.md) | [Session Plan](./week1/session-plan.md) (for mentors) | [Assignment](./week1/assignment.md) | + +## Module Learning Goals + +> [!TIP] +> Learning goals should be a list of outcomes, rather than a list of topics. For example, instead of "Synchronous vs Asynchronous", write something like "Explain the difference between sync and async code execution in JavaScript" + +By the end of this module, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` + +## Prerequisites + +> [!TIP] +> Some modules build on the learning goals of other modules. If that is the case, link them below. If there are no prerequesites, feel free to remove this section. Note that it is assumed that all foundation modules are a prerequisite of a specialisation course and its modules, so in that case you don't have to write them all out here :-) + +You should have completed or understand the learning goals in the following modules before proceeding: + +- [`Module Name`](https://example.com) diff --git a/courses/qa/test-management/week1/README.md b/courses/qa/test-management/week1/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-management/week1/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-management/week1/assignment.md b/courses/qa/test-management/week1/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-management/week1/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-management/week1/preparation.md b/courses/qa/test-management/week1/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-management/week1/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-management/week1/session-materials/example-session-material.md b/courses/qa/test-management/week1/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-management/week1/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-management/week1/session-plan.md b/courses/qa/test-management/week1/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-management/week1/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-management/week2/README.md b/courses/qa/test-management/week2/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-management/week2/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-management/week2/assignment.md b/courses/qa/test-management/week2/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-management/week2/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-management/week2/preparation.md b/courses/qa/test-management/week2/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-management/week2/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-management/week2/session-materials/example-session-material.md b/courses/qa/test-management/week2/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-management/week2/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-management/week2/session-plan.md b/courses/qa/test-management/week2/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-management/week2/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-management/week3/README.md b/courses/qa/test-management/week3/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-management/week3/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-management/week3/assignment.md b/courses/qa/test-management/week3/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-management/week3/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-management/week3/preparation.md b/courses/qa/test-management/week3/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-management/week3/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-management/week3/session-materials/example-session-material.md b/courses/qa/test-management/week3/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-management/week3/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-management/week3/session-plan.md b/courses/qa/test-management/week3/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-management/week3/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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. diff --git a/courses/qa/test-management/week4/README.md b/courses/qa/test-management/week4/README.md new file mode 100644 index 00000000..448996df --- /dev/null +++ b/courses/qa/test-management/week4/README.md @@ -0,0 +1,18 @@ +# `Session Name` (Week `X`) + +This session is about `description goes here` + +## Contents + +- [Preparation](./preparation.md) +- [Session Plan](./session-plan.md) (for mentors) +- [Assignment](./assignment.md) + +## Session Learning Goals + +> [!TIP] +> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible. + +By the end of this session, you will be able to: + +- [ ] `[action verb] [specific skill/knowledge]` diff --git a/courses/qa/test-management/week4/assignment.md b/courses/qa/test-management/week4/assignment.md new file mode 100644 index 00000000..d10d49de --- /dev/null +++ b/courses/qa/test-management/week4/assignment.md @@ -0,0 +1,11 @@ +# Assignment + +> [!TIP] +> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here. + +`Content goes here...` + +## Optional Tasks/Assignments + +> [!TIP] +> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section. diff --git a/courses/qa/test-management/week4/preparation.md b/courses/qa/test-management/week4/preparation.md new file mode 100644 index 00000000..f514351d --- /dev/null +++ b/courses/qa/test-management/week4/preparation.md @@ -0,0 +1,17 @@ +# Preparation + +## 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/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...` diff --git a/courses/qa/test-management/week4/session-materials/example-session-material.md b/courses/qa/test-management/week4/session-materials/example-session-material.md new file mode 100644 index 00000000..c9e34db6 --- /dev/null +++ b/courses/qa/test-management/week4/session-materials/example-session-material.md @@ -0,0 +1,6 @@ +# Example Session Material + +> [!TIP] +> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it! + +`Content goes here...` diff --git a/courses/qa/test-management/week4/session-plan.md b/courses/qa/test-management/week4/session-plan.md new file mode 100644 index 00000000..c189c0eb --- /dev/null +++ b/courses/qa/test-management/week4/session-plan.md @@ -0,0 +1,28 @@ +# 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. + +## 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.