I believe that the strongest instrument for filtering such a-low-quality tests is a code review. You can power-up your code review with mutational testing techniques which will help you to detect the tests which probably do not introduce any value to the overall project scope.
Here is the example of mutational testing framework where you can pick some ...
Recognize that there is a large organizational problem.
Management have to change and give true leadership
Talk to management about:
developer training & education
The risk of not having quality tests
senior developers leading by example
the affect on revenue (bugs and rework)
the effect on customers (bug and rework)
the affect ...
Some things which seem to have worked for the teams I've worked in:
Get permission, record what you do of the below, then present the final result to your colleagues to get them interested in developing better tests. Make sure you don't end up insulting anyone's talent - we all have to start somewhere! It might be tempting for illustration purposes, but don'...
I think you can just take any low-rated application from any application store and it will be highly-likely a "bugged mobile app".
Another option is to install early-access application. Here is the example for Google Play Market:
If you know how to use test techniques such Scenario Testing, Domain Testing and Combination Testing, you can design different kind of tests for each feature in the app, in order to have good test coverage.
If you not, a good intro would be BBST resources:
Video - http://testingeducation.org/BBST/testdesign/
Book - https://www.amazon.com/Test-Design-...
You can capture mobile app traffic and simulate back-end calls using JMeter.
JMeter comes with a proxy server, You just have to configure JMeter proxy so that it can capture mobile traffic.
For more information on Mobile Performance testing with JMeter please refer to this article.
Mobile Performance Testing
How to improve Testing Culture:
Mob sessions to help the devs start to go through worked examples and see what good tests look like vs. Bad so they can learn through
Code reviews, to go through change sets ans see what code has been commited and feedback to thr dev about the test added.
Start hosting regular "lunch and learn" or "tech develops ...
A test at it's best is just a Boolean question to the SUT.
In a similar situation, I would try to map each found defect( from defect database) back to these test cases. And will try to find out (as a team) did we ask the right questions and particularly what questions are missed out and why?
If most of the tests are meaningless, then many defects will not ...