Day 14🚀
Built a Selenium + Python + pytest automation framework
10 test cases. Page Object Model. HTML reports.
Results?
Login suite → 5/5 PASSED
POM suite → 5/5 PASSED
Watching a real browser execute my code = game changer
#QA#AutomationTesting#BuildInPublic#Selenium
Day 12 🔌
Started API testing with Postman today moved from testing what users see to testing what happens behind the scenes.
GET. POST. PUT. Status codes. Response validation.
Different skill. Same mindset. 🎯
#QAEngineer#APITesting#ManualTesting#LearningInPublic#Day12
Bug found on DemoQA 🐛
Email field shows ✅ green tick when completely empty, users think they filled it correctly they didn't.
False confidence is a UI bug too👀
#BugOfTheDay#QAEngineer#ManualTesting
Day 9🔁
Found this on DemoQA today:
Email field shows ✅ green tick even when completely empty
That's not validation that's false confidence🐛
Users think they filled it correctly, they didn't.
UI bugs are sneaky like that.
#BugOfTheDay#QAEngineer#ManualTesting#Regression
🐛 Bug of the day:
App: Guru99 Bank Demo
Action: Logged out → pressed Back
Expected: Redirect to login page
Actual: Protected banking data still visible! 🚨
Severity: Critical
This is why QA exists. 🔍
#BugOfTheDay#QA#ManualTesting#SoftwareTesting#LearningInPublic
Found a Critical security bug today 🚨
A banking app showed protected data after logout back button bypass!
Also built:
✅ Web App Testing Checklist
✅ 5 Agile sprint scenarios
✅ 4 bugs in exploratory session
Week 1 done. 🔍
#QA#ManualTesting#WebApp#LearningInPublic#Day7
Day 6/120: Tested like a detective 🕵️
No script. Just a charter and the app.
Bugs my 25 test cases missed:
→ Login accepts spaces silently
→ Back button behaves unexpectedly
Exploratory testing = structured curiosity.
https://t.co/9q3ZYtudkc
114 more to go 🙌
#QAEngineer#Day6
Day 5 of Revisiting the Roots 🌱
SQL day today, not new to it just connecting it to real QA work now.
Testing isn't just what you see.
It's what's in the database. 🧠
115 more to go. 🙌
#QAEngineer#SQL#LearningInPublic#ManualTesting#Day5#Testing
Honestly knowing what NOT to test. As a beginner it feels like everything needs to be tested. But learning to prioritize test coverage and decide what's critical vs what can wait that's the real skill I'm working on.
Starting my QA journey right now actually!
I chose Manual first, because I believe you need to understand HOW an app works and WHAT to test before you can automate it.
Automation without manual thinking is just scripting blindly.
Quality vs speed is a real battle.
I think the key is making the cost of bugs visible not just to developers but to the business too. A bug in production costs 10x more than catching it during testing. That's the argument that shifts mindsets.
As a QA Engineer, I know the struggle of facing criticism for prioritizing quality over speed. It can be isolating. How do you navigate the pushback from teams eager to release? Have you found strategies to balance quality with business pressures? Let’s share our truths. #QAInsights
As a QA Engineer, 2026 feels like a year where Quality Assurance is moving beyond the traditional role of being the “last line of defense” and becoming a more strategic part of building reliable systems.
Today, QA is increasingly about ensuring trust, accountability etc.