36 Days of Web Testing by Robert Lambert

36 Days of Web Testing by Robert LambertA couple of days ago I found the ebook from Robert Lambert (@Rob_Lambert) “36 Days of Web Testing”. The book is free and covers testing topics like:

- Cross Browser
- Multiple tabs
- Browser extensions
- URL changing
- …

The book is a nice overview and provide lots of useful hints and tips as well as great links to further information about how to test an web application. Go and get it.

http://thesocialtester.co.uk/36-days-of-web-testing-ebook/

Greets Daniel!

[News] Founded the Software Test User Group Rhein Main

Software Test User Group Rhein Main - STUGRMLast week I founded the “Software Test User Group Rhein Main – STUGRM” for all people who are interested in the topic of software testing, quality assurance or software development in general. My goal is, to meet and to exchange about testing topics on a regular basis in the region of Frankfurt, Wiesbaden, Mainz or Darmstadt.
To have a central place for online discussions I created a XING group (STUGRM on XING), user group meetings will also be tweeted from the  twitter account @stugrm.
If you want to participate in the user group, drop me a comment here, follow me on twitter or get in contact with me on XING.

I am looking forward to interesting user group meetings!

Have fun!

Appium on Sauce – A new tool for testing your iOS apps in the cloud

Two days ago Sauce Labs introduced a new tool for iOS test automation: Appium on Sauce. Appium on Sauce is able to automate hybrid or native iOS apps. The new tool based on the open source tool Appium written in Node.js. Currently the tool support iOS devices only but Android support is on its way.
Appium uses Selenium commands and map these commands into a format for UIAutomation. It uses the WebDriver JSON Wire Protocol to drive UIAutomation.
Sauce Labs says, the tool requires no recompiling or modifications on the app you want to test. Tests can be written in any programming language and testing framework using the Selenium API. Appium on Sauce needs no setup and no maintenance. Tests can be run in parallel across several machines in the cloud. CI support is also included.

Appium on Sauce

Appium on Sauce

Currently the tool is only available by invitation to see if the environment is stable enough to handle many users and apps in parallel. For me this tool looks very promising and we will see how well it can be used.

See Appium on Sauce in action:

Greets

Top 10 Mobile Application Testing Automation Tool Requirements by Brian MacKenzie

First, Happy new year to everybody! The year has just started and I want to continue writing posts about mobile and testing in general. During my vacation I found this really interesting blog post from Brian MacKenzie “Top 10 Mobile Application Testing Automation Tool Requirements“. This post is a really good summary of the requirements, if you are looking for an automation tool for your mobile apps!
The top 10 requirements are:

  1. No jailbreaking or rooting devices
  2. True object recognition
  3. Integration with existing Integrated Development Environments (IDE)
  4. High reusability of scripts
  5. Physical device and emulator/simulator support
  6. Web application support
  7. Data driving, screen capturing and standard reporting capabilities
  8. Support for common interruptions and functionality
  9. Manual or automatic (scheduled) execution
  10. Integration with performance testing tools

What do you think about the requirements?

Find the complete post here.

Mobile App Update Testing

During the development process of mobile apps manual and automated testing is highly recommended. But there is another test you should do before releasing or submitting your app to a store. Testing the update procedure! Testing the update procedure from the current store version to the new release candidate is really important and it is often not done by developers or QA experts. With this test you verify, that the new app is not affecting the old installed version. Here are three facts that will be covered with that test.

Test that the update…

  • … will not logout a user from the app e.g. before the update he was logged in.
  • … will not affect the local database e.g. existing data will not be modified or deleted.
  • … will be installed correctly from the store (simulation).

You can also test the update from far older versions to the latest one, to see what is happening.
For the two big players Android and iPhone I will describe, how to test the update from one version to another using different tools.

iOS
On the iOS side there are two ways of testing the update procedure. The first one can be done with iTunes. See also the Technical Note TN2285 from Apple.

  1. Build an adhoc app version of the app that is currently live in iTunes store. HINT: This version must have the same bundle identifier as the new app.
  2. Be sure that no older versions of the app are installed within iTunes and on your test iOS device (Sync with iTunes to be sure).
  3. Drag the app from step 1 into iTunes and sync the version to your test device.
  4. Launch the app and do some manual testing to see that the app is working.
  5. Build the new release candidate version of the app and drag it to iTunes and sync to the device. iTunes should confirm, that the older version will be removed. HINT: DO NOT delete the old build! In the next step iTunes will install the new app over the old one and will simulate the update from the app store.
  6. Launch the new version and see if everything is ok.

The second way of testing the update procedure for iOS is using the iPhone Configuration Utility. Using this tool is more comfortable, especially if you want to test the update procedure on more iOS test devices like iPhone 3G, iPhone 3GS, iPhone 4(S), iPhone 5 or iPads.

  1. Build an adhoc app version of the app that is currently live in iTunes store. HINT: This version must have the same bundle identifier as the new app.
  2. Be sure that no older versions of the app are installed on the test device.
  3. Install the app from step 1 to the devices you want to check.
  4. Launch the app and do some manual testing to see that the app is working.
  5. Build the new release candidate version of the app and install it with the tool. The update procedure will be simulated.
  6. Launch the new version and see if everything is ok.

Android
The same can be done also on the Android side. To test the update for Android you can use adb to simulate the procedure.

  1. Install the current Google Play store version of your app to your phone.
  2. Check that the version is working.
  3. Build a release candidate of the Android app. HINT: Be sure to sign the release candidate with the Play store keystore.
  4. Use the following command to test the update procedure:
    ./adb install -r APPNAME.apk. The option -r means reinstall the app and keeping its data.
  5. The new version is now installed and can be tested.

That’s it! Try it for your next release!

Greets!

Tap Into Mobile Application Testing by Jonathan Kohl

Mobile mobile mobile is everywhere!
If you are in the field of mobile app testing you maybe want to read the book “Tap Into Mobile Application Testing” from Jonathan Kohl (@jonathan_kohl). Jonathan gathered lots of very interesting topics about mobile app testing. His book ist currently in a beta phase! If you buy the e-book now, you get all the updates for free. The book costs $14,99 and you will get a PDF, EPUB and MOBI format to read it of course on your mobile device!Tap Into Mobile Application Testing

In this book, you will learn:

  1. How mobile devices work: features, affordances and how to effectively use them when testing.
  2. How to use thinking tools to provide structure to your testing and test idea generation.
  3. How to test and recognize common failures on devices.
  4. How to log bugs well on mobile projects.
  5. How to create a test strategy that makes the best use of your time and resources.
  6. How important it is to incorporate physical movement into your testing.

Get the book here.

Greets!