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

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...
Post a Comment
Read more

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
15 comments
Read more

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...
Post a Comment
Read more