It’s January. Which means the State of Testing Survey 2017 has gone live. This is a worldwide survey that tries to identify the existing state of testing. Taking the survey is one step into bringing more transparency into our profession. If you are a tester, please consider participating in the survey. Like most surveys, you will receive a report with […]
State of Testing Survey: 2017
BrowserStack Live: Running manual tests on the cloud
Ever wanted to quickly see if you can reproduce an issue on a specific combination of browser version and operating system? In this post, we will show you how to use BrowserStack’s Live offering to test your web and mobile applications across a wide range of browser and operating systems. Why this post? We work with startups. Many times, our […]
Selenium- Firefox/geckodriver installation issue
Problem: Our selenium scripts started failing when we were running our tests on Firefox browser version 47 or higher. After a little bit of research we came to know that Selenium WebDriver 2.53.0 is not compatible with Firefox 47.0 or higher. The WebDriver component which handles Firefox browsers will be discontinued and we had to use geckodriver instead. Why this […]
Testing the Fitbit heart rate monitoring system: Part 2
In this post, we outline a cheap and creative way to perform repeatable and controlled tests on the Fitbit heart rate monitor. Our test has a reasonable degree of accuracy. We hope it helps the Fitbit developers rapidly test their prototypes. To be clear: thorough, accurate and precise testing is needed in the later stages of development. The test outlined […]
Testing the Fitbit heart rate monitoring system: Part 1
We outline a quick and dirty test for testing Fitbit’s heart rate monitor. This is the first in a series of two posts that will cover our work on developing a cheap and quick test with an acceptable level of accuracy for the Fitbit heart rate monitor. Why this post? The ‘why’ behind this post is long. You can safely […]
Selenium to get browser console log
The browser console log, along with debugging also helps us capture errors that occurred when using a web application. Your developers will thank you when you include console errors in your bug reports. As part of running your GUI automation, it is a good habit to check and report the errors present in the browser’s console. In this post, I […]
Comics for easier conversations – November 2016
This is part of the series of ‘Comics for easier conversations’, in which I share work related cartoons. This November post has comics related to work scenarios like missing an important detail, deadline dates and applying a new concept. Listed comics: 1) When you are testing a few functionalities and as an oversight, you missed an important one. 2) At […]
Comics for easier conversations at your workplace
This post gives you a few comic strips and a related work scenario to use them. I like comics and comic strips. I actively use comics at my workplace. Comics make it easier to make my point. I use images which set contexts and help me frame or re-frame my point of view. In this series of blog posts, I […]
Better pytest failure summaries
We, at Qxf2, are really liking pytest. It is the most Pythonic test runner we have come across so far. We started using it with our GUI automation. We realized one thing very quickly – pytest’s reporting capabilities are configured to suit unit testing. We needed to reconfigure pytest’s reporting to suit our GUI automation framework. It was also hard […]
pytest: Cross browser, cross platform Selenium tests
We showed you how to run tests on BrowserStack using pytest in our previous post – pytest and Browserstack. We had an example test and ran it across one browser from the command line argument. What if we need to run it across different browser versions, platforms and platform versions? Why this post? pytest responds really well when we run […]