Your Portfolio QA Pack
The capstone project for QA Testing & Software Testing: From Your First Test Case to Your First QA Role — a free Data & Tech course. Pass it and you earn a certificate anyone can verify.
- Most courses free to start
- 7 steps
- Pass mark 65%
- Graded within minutes
- Beginner-friendly
The project unlocks once you complete the lessons. The workbook is free to download now so you can see exactly what is expected.
What you will submit
One public link: a Google Drive folder or Google Doc with view access, or a public GitHub repository, containing Parts 1 to 6 (and the bonus if you did it), with screenshots and evidence inside.
What to do, step by step
- Part 1. Choose ONE feature to test on a practice site built for testers (for example the Sauce Labs demo store at saucedemo.com or a page on the-internet.herokuapp.com), or on an app you legally use as an ordinary customer. Name the site or app and the feature. Never probe systems for weaknesses or use anyone else's account or data.
- Part 2. A one-page test plan: what you are testing and why, in scope and out of scope, the techniques you will use (at least equivalence partitioning and boundary values), the environments (device, operating system, browser, network), the main risks, and when you will call testing done.
- Part 3. At least 10 test cases in a table (ID, title, preconditions, steps, test data, expected result, actual result, status), including at least 3 negative cases and 2 boundary cases. Run them and record the results honestly.
- Part 4. At least 3 bug reports, each with a clear title, steps from a known starting point, expected and actual results, severity and priority with a one-line reason, environment, and evidence (a screenshot, a screen recording link or the exact error text). If the site is a practice site with deliberate bugs, those count. For each bug, state its lifecycle status and what must happen for it to be closed.
- Part 5. One exploratory session note: the charter, the time box, what you tried, what you found, and the questions it raised.
- Part 6. One API test against a practice API (for example JSONPlaceholder) using curl or Postman: the request, the response status and body, what you checked, and one negative test such as a missing resource.
- Optional bonus: a small automated test (for example Playwright) with a screenshot of it passing, and a one-paragraph note on anything an AI assistant helped with and how you checked it.
Files to work with
Project workbook (fill in, then submit)The whole brief, an evidence checklist, the grading rubric as a self-check and the link-sharing steps in one file. Opens in Word, Google Docs or WPS.Word · 6 KBHow it is graded
| Criterion | Weight |
|---|---|
| The test plan is specific: scope, techniques, environments, risks and exit criteria for the chosen feature | 15% |
| Test cases are complete, observable and runnable, cover negative and boundary cases, and have honest results | 25% |
| Bug reports are reproducible from the steps, with correct severity and priority, evidence and lifecycle status | 25% |
| The exploratory note shows a real charter, time box, findings and questions | 15% |
| The API test shows the request, the response, what was checked and a negative case | 20% |
You need 65% overall to pass. A failed submission comes back with feedback and can be revised and resubmitted once free; further attempts come with the All-Access Pass or as a paid retake.
Before you submit: make your link public
If your work lives in Google Drive or Google Docs, open Share → General access and change “Restricted” to “Anyone with the link” (Viewer). Then paste the link into a private browser window: if it opens without sign-in, you are ready. A private link cannot be graded — it is the single most common reason a good project fails.
Frequently asked questions
Do I have to finish QA Testing & Software Testing: From Your First Test Case to Your First QA Role before submitting the project?
Yes. The submission screen opens once every lesson in QA Testing & Software Testing: From Your First Test Case to Your First QA Role is marked complete. The lessons are where the methods, the local context and the worked examples the project depends on are taught.
How is the project graded?
An examiner scores each rubric criterion from 0 to 100 and weights them as shown on this page; you need 65% overall to pass. Most submissions are graded within minutes and you get written feedback on what was strong and what to improve.
Can I resubmit if I fail?
Yes. A failed project comes back with feedback; revise the weak parts and resubmit. A passed project is final — the certificate is issued and cannot be re-rolled.
What do I actually submit?
A write-up of what you did (under 5,000 characters) plus a public link to your work — a Google Drive folder, Google Doc, spreadsheet, GitHub repository or video. The link must open without sign-in; a private link cannot be graded. The free project workbook on this page walks you through all 7 steps.
Is the certificate real?
Yes. Passing this project issues a certificate with a unique verification code. Anyone — an employer, a client, a school — can open the verification page and see that the certificate is genuine and which project earned it.
More Data & Tech projects
- Sales Dashboard for a Local Business
Data Analysis Foundations
- My Skillnaija Frontend Portfolio
Frontend Web Development
- Your First Programs, for a Group You Know
Coding Foundations: Think Like a Programmer
- Your Junior Technician Field Pack
Data Centre Technician: Racks, Power, Cooling, Cabling and Remote Hands
Ready to earn this certificate?
QA Testing & Software Testing: From Your First Test Case to Your First QA Role is self-paced. Finish the lessons, complete this project, and the certificate is yours to share.
Start learning free