Let me share with you one of the two articles that unveils common mistakes typically present in most QA and iOS work flow. In this section, I will demonstrate the number of bugs I came across within my projects. For instance, four projects were full of minor mistakes and 30-40% of general time was spent on figuring out and further elimination of these bugs. The following examples contain screenshots of the specific problems.
How does Lemberg ensure quality of our mobile apps? What tools do the Lemberg QA team use to check mobile apps? This blog post is part of our own development knowledge hub on mobile apps testing.
This article is the continuation of the series of Lemberg`s blog posts about developing applications for location tracking. In this post, Lemberg’s QA team will share some practical tips about testing the GPS accuracy of devices, which for sure is essential for the development of apps with location tracking functionality. Find out...
Test, Double-test, and Triple-test
For some time now, we have been working on improving a location tracking feature for one of the agencies we collaborate with. The QA process for location tracking is expectedly different from that of other features, simply because location tracking must be tested in a real environment and there is no way around it. It is best practice to assess the app in different conditions, to make sure that it works as expected and under all circumstances.