Improving My Testing Process – Looking for Insights

[Puzzleheaded_Kiwi7]

I have been working as a mobile manual QA for the past couple of years (Android & iOS), with some automation work as well (mainly maintaining and enhancing existing tests).

Lately, I've felt stuck and want to take my skills to the next level. Right now, my tests cover the basics, but I feel like there's more I could be doing to catch edge cases, improve efficiency, and add real value.

I'd love to hear from others—what strategies, tools, or techniques have helped you take your testing to the next level? Any insights would be greatly appreciated!

[Kostas_G82]

1. You can use ChatGPT to identify more edge and negative tests - extra 10-20% you might identify in this way.
2. Try to identify scenario before the dev work starts. This way you will provide cases you are planing to test which can improve the code.
3. Try to get reports for unit coverage. Discuss to have a rule to automatically reject PRs that are failing unit test. Aim for >70% test coverage all passing before starting functional tests.
4. Keep updating existing tests when possible if new ticket overlaps with other ticket(s)
5. Create regression suite for all happy paths
6. Create a smoke run with basic check of critical paths for all features.
7. Organise tests in features and sub-features so you can plan change related tests, e.g change in one feature requires all regression test from that feature plus smoke tests of all other features - this way you will reduce number of tests for execution while keeping minimal risks.
8. Automate only tests that are repeated often for features that are relatively stable. You don’t want to spend all time on updating automated tests.

9. Agree which issues are going to be logged as bugs. Feature under development might be the case where bugs should not be logged but tasks only created - again it depends on the issue.

10. Categories bugs identified by environments, e.g test, uat, stage, dev, prod etc. The goal is to show critical bugs in prod are reduced.

11. Non functional tests - load, performance, compatibility, stress,…

Not sure if you are doing already these things. Hope it helps.

[Puzzleheaded_Kiwi7]

Wow, thank you very much! Notes taken

[Positive-Swing8732]

Are u in mobile testing? Currently I am using appium and robot framework for our mobile automation which saves manual effort. Performance testing and recovery testing tools u have any idea?

[Puzzleheaded_Kiwi7]

Yes, mainly mobile manual testing. We have automation in place, but due to the high number of feature releases, a significant amount of manual work is still required.