Skip to main content

QA First World Problems

We have recently created an automated test suite to replace some of the manual tests that we used to run for regression. I'm finding the below more of an occurrence now!


Labels:

Comments

  1. halperinko20 August 2013 at 22:11

    If you don't build your automation logs well - this will become:
    "I have to spend 3 days investigating a failed automated test, rather than spending a whole day running manual tests."
    Drill-down logs infrastructure is highly required, yet, hardly any common tools for that.
    @halperinko - Kobi Halperin

    ReplyDelete
    Replies
    1. Gareth Waterhouse21 August 2013 at 00:23

      We've set up our automated tests to give us as much information as possible when they fail, a screenshot is captured and the assertions all have pretty descriptive error messages. When debugging we'll see the stack trace as much as possible, so it's not all doom and gloom.

      All too often however, tests don't have informative errors or it's difficult to find out why a test failed, then you'll get your 3 days investigating!!!

      Delete
  2. Zdeněk Šrámek17 April 2018 at 07:32

    BitTorrent enables folks to share substantial information with one another using a peer-to-peer network, which indicates they share portions of the file with one another, rather then downloading the whole file from a central site (such as iTunes).

    MacGIC - Get all Mac Tools at One Place!

    ReplyDelete
  3. mohit28 November 2018 at 03:34

    Thank you for sharing your article. Great efforts put it to find the list of articles which is very useful to know, Definitely will share the same to other forums.

    runkeeper

    ReplyDelete

Post a Comment

Popular posts from this blog

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more