Looking for remote work in Africa? Find it on workafro.com →

First jobs · 2 min read

Software testing practice for entry-level applicants in Kenya

Learn to write a reproducible bug report using a fictional sign-in form and a cross-browser check.

A person works on a laptop in an office. Illustration.
Illustration for this guide

An entry-level software testing portfolio can show how you observe a problem and explain it clearly. It does not need access to an employer's private system. MDN's cross-browser testing guide explains why a website should be checked across different browsers and devices. The scenarios below are fictional exercises created by work.ke, not an employer's test. Only test systems you are authorised to use; never try to access someone else's account or private data.

Exercise 1: describe a sign-in problem

Imagine a sample form should show “Enter an email address” when submitted empty. On your test page, pressing Submit does nothing. Write a report with:

1. A short title: “Empty sign-in form does not show an error”.

2. Your test environment: browser, version and device, if known.

3. Steps: open the authorised test page, leave the email blank and press Submit.

4. Expected result: an understandable validation message appears.

5. Actual result: no message appears.

Add a screenshot only if you have permission and it contains no sensitive information. Do not claim you found this problem on a real employer's site.

Exercise 2: compare two displays

Open your own simple sample page in two available browsers or screen sizes. Record whether the menu is usable, the text is readable and the form can be completed. A difference is worth investigating; whether it is a defect depends on the stated requirements.

Exercise 3: test an edge case

If a test form accepts quantities from 1 to 10, check 1 and 10 as well as values outside the range. Record the expected behaviour from the requirements, not from a guess. Ask a mentor when the requirement is unclear.

Present your work honestly

Share a short practice report with a fictional URL and dummy data, the steps and what you learned. If you have not used SQL or API tools, do not list them as professional experience. Check each employer's current role, experience requirements, location and application route before applying. Never pay for an interview.

Sources and further reading

Explore this topic