Maintaining a Mobile Device Lab – Neotys Testing Roundup

1. Mobile Testing: How to Maintain Your Devices

Mobile testing is such an important part of testing today, and something we at Neotys take very seriously. That’s why this blog post caught our eye.

Maintaining the devices that your company provides for testing mobile applications is mandatory for the success of your mobile development projects. It is as important as the human resources of the company. Since modern emulation tools and cloud services don’t assure high quality of mobile applications, all portable devices such as smartphones and tablets should be maintained properly.

This article explains how you can extend their lifespan.

2. Using Business Decisions to Drive Your Testing Coverage

In a business setting, software testers have a great challenge: to articulate how they support the business lines. One way to approach this is by addressing the business decisions—and there are plenty around. Use them to drive your testing activities and increase the business decisions being covered by testing.

One great piece of advice offered in this post is to ask questions that reveal where business decision points are. For example:

  • Are we ready to release the solution?
  • Do we comply with the explicit requirements?
  • Are we ready to start user acceptance testing with the client?
  • Are we on top of things, and is testing on track?

There’s more where that came from. Check out the rest here.

3. What is Integration Testing and How It is Performed?

Sometimes it’s nice to go back to the basics, even if for no other reason than to remind us why we do the things we do. This blog post addresses the topic of Integration Testing: the combination in Test of many modules which are tightly coupled with each other.

Once all the individual units of a product are created and tested, we can combine those “Unit Tested” modules and start doing integrated testing. So the meaning of Integration Testing is quite straight forward – Integrate/combine the unit tested modules one by one and test the behavior as a combined unit.

This blog post is a comprehensive review of an important subject in software testing.

4. Discussion: Should load test validate functionality?

Here’s a discussion, posted by software tester Erki M, that’s worth contributing to:

I am developing a loadtest to a customer who is saying that if a certain response contains “bla:bla” I should execute a different path in load test. On client side it means that a certain button is disabled and user should not be able to push it. On the other hand, if I ignore the mark-up and send it anyway, the server is perfectly fine with it (means it returns HTTP.200). So the customer is demanding that I check for this condition, for me I would mean that I had to parse all the responses of this type and decide which path to take, and this seems absurd. My reasoning is that the server should tell me to get lost. So the point is that data is not being validated on server side (which is a noticeable security issue), but I have been forced to write a ‘hack’ to deal with this. I am not generally against parsing responses, ie, due to browser implementation, it might be totally ok to return unauthorized with HTTP.200, but the question is – to what extent should I tolerate parsing the responses?

What do you think? Take part in the discussion.

Leave a Reply

Your email address will not be published. Required fields are marked *