When a banking app fails, a payment disappears, or a digital service goes down, who should be held accountable?
The tester? The developer? The technology leader? Or the organisation?
Software quality is everyone's business.
What's your take? 👇
#ANST2026#SoftwareQuality
If you want to become a software tester, don't wait until you feel “ready” to start building your portfolio.
Pick an application.
Test it.
Document your approach.
Write test cases.
Report bugs.
Explain what you found.
Your portfolio should show how you think.
Testers, you're given a new application to test.
You have 30 minutes.
What's the FIRST thing you do?
A. Start clicking around
B. Read the requirements
C. Identify the critical user journeys
D. Look for the riskiest areas
Tell us your answer and why.
A tester doesn't ask only:
“Does it work?”
They also ask:
“What happens if…?”
What if the field is empty?
What if the user clicks twice?
What if the network drops?
What if the input is unexpected?
That's where testing gets interesting.
Want your first software testing job?
Don't spend months collecting certificates without practising.
Learn the fundamentals.
Test real applications.
Build projects.
Get feedback.
Document your work.
Build evidence, not just credentials.
Test an application.
Document your approach.
Write test cases.
Report defects.
Show your evidence.
Your portfolio should demonstrate what your CV claims.
Your CV says:
❌ "Experienced in API testing."
But what can you actually show?
Can you:
→ Create API test scenarios?
→ Validate responses?
→ Test error handling?
→ Verify data?
→ Document your findings?
Don't just list skills. Build evidence of them.
Testers, let's settle this. 👀
You open a brand-new application for the first time.
What's the first thing you do?
A. Read the requirements
B. Explore the application
C. Look for obvious bugs
D. Start testing the critical user journey
What's your answer and why?
TESTING TIP
Don't only test what the user is supposed to do.
Test what they might actually do.
Empty fields.
Wrong inputs.
Double clicks.
Unexpected characters.
Network interruptions.
The happy path is only part of the story.
Want to break into software testing?
Don't make the mistake of trying to learn everything at once.
Start with the fundamentals.
Practise what you learn.
Get feedback.
Build evidence of your work.
Progress beats trying to know everything.
SQL is one of those skills that can change how you test.
Instead of only asking:
"What does the UI show?"
You can ask:
"What actually happened to the data?"
Learn to test beyond the screen.
Good testers don't only ask:
"Did it pass?"
They ask:
"What does this result actually tell us?"
That's the difference between executing tests and exercising professional judgement.
5 things to look for when testing a login page:
- Valid credentials
- Invalid credentials
- Empty fields
- Account lockout
- Password security
Then ask:
"What happens if I do something the developer didn't expect?"
That's where testing gets interesting.
If you're trying to break into software testing, build a portfolio.
Don't just write:
"I know API testing."
Show:
- API collection
- Test scenarios
- Defects found
- Evidence
- Test report
- Your conclusions
Show, don't tell.
A test result without context can be misleading.
"95% passed."
Sounds great.
But:
What was tested?
What wasn't?
Which risks remain?
What evidence was collected?
Numbers don't create confidence. Context does.
You don't need to know everything before becoming a tester.
But you should be willing to learn:
🧪 Testing principles
🔍 Investigation
🗄️ SQL
🔌 APIs
🤖 Automation
📊 Evidence
🗣️ Communication
Curiosity is one of your biggest tools.