Mobile application testing represents a great challenge nowadays. Lots of factors has to be considered and it is critical to ensure that clients have a positive experience when they use the mobile applications. Keeping in mind that the customers do not want to be treated like guinea pigs is essential. When they find a flaw, you’ll never hear a word from them and they certainly won’t come back.
In Merit Solutions, we use our own mobile application testing checklist when testing our mobile applications. The list below is its general representation and we use it in order to ensure the highest quality to our clients. The list does not include security checks, since this is a very wide and important area of testing which surely deserves separate article.
Agile teams usually have people with different competencies. Collaboration between team members is essential for the success of such teams.
In agile teams, there is a potential conflict of interest and opinions between developers and testers. Developers can feel bitterness and frustration when facing the testers’ bug reports and the discussions whether the bugs should be fixed or not can get heated and nasty. On the other hand, testers become the focus of blame and an easy target when bugs are released into production. From the upper management perspective, this “battle” is often perceived as productive, since it makes the projects move faster, but if the conflicts become too frequent and too personal, it may affect company’s everyday work and internal relationship, which can ultimately lead to the unsuccessful projects. Therefore, company managers should ensure that the team members have mutual respect for each other and to prevent thinking that the testers are troublemakers and vice versa. Product quality is a team sport and quality mentality should be facilitated among team members. At the end of the day, the clients’ needs come first and they will certainly be happier if they get high-quality product.
If you are using Xamarin.Forms to develop a UI for your mobile app, then you probably feel crippled by the lack of a designer. It can take a couple of minutes when making a simple change in your XAML file until you can see your change in action on your favorite emulator or device. This lag is known to cause a lot of frustration for developers working on UI design and can negatively influence productivity.
The variety of different possible mobile configurations can present a huge challenge for mobile application development. From a superficial perspective, it seems that mobile emulators present an easy answer to complete mobile applications development and testing, but is it the whole truth?
Xamarin.Forms behaviors lets you add functionality to user interface controls without having to subclass them. Attach Behaviors extend object functionality without writing a new control. In this video we will show the example of validating user inputs.
Exploratory testing is investigative testing practice, which involves simultaneous learning about the software under test while designing and executing tests, using feedback from the last test to inform the next. Because there is a common misunderstanding that exploratory testing means simply “execute random actions and see what happens,” it is important to emphasize that this is a very rigorous approach. The same kinds of test design analysis techniques and heuristics are used in exploratory testing as in traditional test design, but the tests are executed immediately. The test design and execution becomes inseparable, a single activity.
If you are developing Android mobile applications, chances are that you are going to need some kind of localization and internationalization. And if you are targeting multiple mobile platforms - you would most likely prefer to do that job in one place.
The use of Xamarin Forms, PCL projects and paradigms such as MVVM allow for a great code sharing between all the different platform projects. Ideally our solution for localization:
Should be based on resource files
Resource files should be maintained in only one project
Here is when resx files come into the game. Resx is very simple and powerful resource management solution, where you can add or remove string, image, audio and video effortlessly.
Xamarin’s Signature Pad control makes adding, changing, opening and saving signatures much easier. This example will show how to do basic operations like loading a signature from an array of points, saving a signature as an array of bytes, and exporting users' signatures as an image.
LoadUI is a fully interactive drag-and-drop interface which allows users to create performance tests. With LoadUI, users can easily add or remove components and follow test statistics on the Statistic tab. For my testing, I use the Fixed rate, DataSource, SoapUI Runner and Table Log components:
Fixed rate sends trigger message at a specified fixed rate.
DataSource allow attaching CSV files to incoming Virtual Users.
SoapUI Runner uses values from DataSource. User can create project in SoapUI and use it.
Table Log displays incoming messages in a tabular format.