A Test Automation Blog

Our test automation suite for a single page application (SPA) called service-hub , takes almost one hour to run all +- 200 scenario's in serie per browser. The amount of scenario's will keep on growing with the expansion of the product. So I needed to start using some clever tricks to speed up the process. One of those tricks is by testing in parallel sessions. This is a very good thing to figure out anyway, but is also taking more resources (and therefore cost more money). Another trick is by using the API for some of the preconditions that take a lot of time. But for that we need a token which is stored in the browsers Session Storage. Scenario example For the service-hub product which I'm testing, it takes precious time to add/remove a material from an activity if I need to do this all via the UI. There are many steps to take to make sure I'm on the correct page, tab, breadcrumb, sub-tab and finally the element and to cover all other scenario's that might

On most websites and applications you might need to fill in a form of some kind. Some people like to `click` in each field with the mouse, others like to use the `tab` button on the keyboard. But do you need to script both of these scenario's for your automated tests? https://www.service-hub.com/ contact form What to test and why? There are a bunch of additional questions that pop-up in my mind when I ask myself the question: "`Click` or `Tab`, which will be required in our test automation suite?". Because sure, we can automate both scenario's, but why is this needed? Would it be sufficient to automate only one of these? Can we mix them (most fields click and only one tab)? Will automating it save us time/effort?  The answer is simple: "It depends on what you want to test and what the test should be covering".  If you want users to navigate through the website with keyboard tabs, you should test this. If you want users to navigate through

August has ended and Google released new statistics . So let's see what changed since they published the  Android statistics of July 2018 . Is Android 9 (a.k.a. Android Pie) showing up in the statistics already? Will Nougat start show a decrease in market share? Let's find out, here are the facts. https://developer.android.com/about/dashboards/ Statistics, facts and trends Versions over time Facts about the Android versions compared to previous month: The landscape is still a jungle of versions with no outstanding dominant version and three versions around +-10% market share Android 9 (Pie) is not shown yet Android 8.1 and 8.0 Continue the up trend Android 7.1 is still increasing with almost 1% in a month Android 7.0, 6.0 and 5.1 are showing a steady decrease Android 5.0 and 4.4 are showing a steady decrease up to 0,5% per month Codenames over time Facts about the Android codenames compared to previous month: Android Pie is not shown in