I expect that your remote testers see their job the way it is defined for nearly all the organizations that use them: does the software work and can they sign off on that and get paid.
If you create an arrangement where their pay and employment is dependent on giving much greater feedback it will happen, though you'll need to invest time and training ...
This doesn't have anything to do with cultural difference . It's the issue with organization's work culture . To fix this , you have to ask yourself some hard questions.
How independent is the test team
What are the KPI used to validate QA efficiency
Is bug count and defect detection ratio could be considered as KPIs
Does testers get appreciated and ...
On the other hand, we want to start the test early
This is the key area to examine. If there is a requirement to start testing 'early' then the definition of done should include this. However I see the problem is that now you'll have two definitions of done :(
So in this case I think you might want to consider a 'definition of ready for testing' that is ...
You should get a good understanding of widely used mobile platforms and form factors around the world. The device matrix shared by @dbmunich is a good one. There are many factors to consider before arriving on a similar matrix. There's a vast difference while you strategise testing of a native application versus a hybrid application.
Automate your sanity ...
But the question I ask myself is, how should a test charter be built at all?
In this case we used the tips from Elisabeth Hendrickson.
For example, in our project we used an easy test charta template as followed:
Easy template as example
Investigate a goal with medium/resources in order to find (more) information about it
So what does this mean?
You have to format your test steps as XML:
<steps id="0" last="1">
<step id="0" type="ValidateStep">
<parameterizedString isformatted="true">Step 1</parameterizedString>
<parameterizedString isformatted="true">Result 1</parameterizedString>
According to the Azure DevOps Forum, The Move or Drag & drop test case functionality is currently not available in new Azure Test Plans. It will be available in the coming weeks. For now, you can turn off the “New test plan page” preview feature to return to the old view by performing the following process:
Sign-in into your Azure DevOps Services ...
Magento has its own "testing guide" which seems to cover most if not all of these topics.
Magento also has its own Functional Testing Framework, which you should probably use as it will make live of future developers/testers easier which already know how to write functional tests for their product. See https://devdocs.magento.com/mftf/docs/introduction.html
A good mobile app testing services provider has different options available according to time at offer for mobile testing.
If a quick test run is to be performed on the major mobile devices/configurations, then below techniques can be followed.
Text should be checked on one device as it will be same on the others as well. So only the layout/breaks need to ...
SonarQube also checks for security vulnerabilities (check beforehand if your application language is supported), see https://www.sonarqube.org/features/security/ .
You can define different rule-sets to scan a project
Users can mark issues as false-positives to discard them from future checks
It can be easily integrated into your CI tool
It has pre-defined ...
We had the same issue in our past. For some reasons we managed that somehow. Because beside testing with simulators we also tested with real devices (since real devices have different behaviour than simulators).
First: Made an overview about the devices with the help of statistic webpage
In case of using real devices you have to consider that you are using:...