In this article, we present an approach of testing the authentication flow of an application with the State Transition Testing technique. We use AltWalker, GraphWalker and Python to write and execute tests automatically.
Built in the Altom test lab, AltTap is a robot designed to help with and mitigate some of the critical challenges of test automation. It is especially useful in scenarios involving the running of tests on devices of varying screen sizes and resolutions. AltTap’s special power is that of performing automated tests on any type of touchscreen device.
How does it do that exactly? It simulates a human tester by the using of a stylus to perform click actions on a touchscreen. The process is based on an image-recognition algorithm.
After watching the WWDC 2015 presentation of the new testing tools that will be available in XCode 7, which promises UI testing and code coverage right inside XCode, I decided to give it a try myself. This blog post is a summary of my experience.
We are happy to announce that part of our team will be heading off to Barcelona at the beginning of March to participate in Mobile World Congress.
I learned a lot of things this Citcon. For those who haven’t got the chance to be part of a Continuous Integration and Testing Conference, below’s a diagram illustrating how it works.
1. The four Ws of BDD
1.1. What ?
BDD (Behaviour-Driven Development) is a concept in which acceptance tests are written as examples that anyone on the team can understand. The process of writing those examples is a collaborative effort of the developers, testers, and the business owner (“los tres amigos”). They decide together if the thing they set out to be built is the right one, before starting implementing it. In doing so, a deliberate effort to develop a shared, ubiquitous language (used and understood by everyone involved in the project) for talking about the system is created.
BDD scenarios are built around…
While testing an iPhone application that is part of a bigger solution developed by teams in different locations, I came across a few issues that made me look into some of the available options for recording the application in use on a real iPhone and I decided to try to build my own testing sled using parts I already had around the office. It turned out that the original iPhone packaging had everything I needed.
I’ve been using RobotFramework with its Selenium Library for web automation for quite a while now and have always had the problem of getting any scripts that use XPath run on Internet Explorer.
For a while now, I’ve been involved in testing a complex media web application developed in Flex, and I got to the point where some help from a tool would have been much appreciated :). I have to admit that this was my first RIA project, so I decided to dig a little bit into it, especially regarding the options one would have in automating some of the functional tests.
Scope
I don’t want to argue about the ROI of an automated GUI test suite, or about the fact that maybe it would be much more useful to automate some other types of testing like unit and performance (there are specific tools for each of these).
All the info from this post can be found on the internet, but it takes a lot of time and trouble to gather and analyze it. This post will provide a list of tools I found that support Flex Automation, hoping it will help you if you’re thinking about functional testing automation for Flex based applications.
The Flash in the blackbox
The main issue with RIA Flex applications is …
