Test automation - parallelism and the questions it raises

The usual disclaimer of 'I don't know what I'm talking about' applies here...

 Lately we have been feeling some software quality hurt - not enough time, not enough people testing, stuff still getting missed and reported as bugs by the customer.  As this is a topic not unfamiliar to me, I decided to do some deeper research, and even attend a local user group to discuss test automation.

 I already knew that 'GUI test bad!  Unit/API test good!', but confirmed with multiple developers that our legacy app simply had a lot tied into the GUI.  That's ok - legacy is where your revenue is, as someone pointed out (possibly at DevOpsDays Toronto?) - so we know that we kinda need GUI testing.

 The user group's consensus was 'you need a test framework', so I figured we needed a test framework and set about building one.  There were a lot of bad reasons for me being the person to do this...but a few good ones, too:
  1. I actually had some time to spare.
  2. I was responsible for deployments/manual post-deploy verification
  3. I was newly responsible for manually smoketesting the staging environment prior to a deploy
  4. I was responsible for monitoring, most relevant being New Relic Scripted Browser Synthetics
Chief among the bad reasons for me writing (anything, really) a test framework was the whole 'I have zero development experience'.  The guy teaching the Pluralsight course (Creating an Automated Testing Framework With Selenium) did a good job though, and I managed to hack together something that not only worked, but was relatively easy for me to expand!

  \o/

So here we are - now have 30-40 pages covered by tests, a 1000-line long helper class (the worst copy pasta), and then I see the browser/platform matrix from QA for the new project coming online soon...

    D:

 I had played with parallelism early on in the framework's life, mainly because I knew how impactful that change would be, but never got anywhere with it.  Now it was super duper a requirement.  So I went back to the problem again and ... got nowhere.  I did, however, manage to get Sauce Labs' example framework running in parallel, but as soon as I tried to transpose that into some of my test cases, nothing worked.

 More digging later and we have this:  Parallelism is hard!  In general!  Even the guy who did the initial Pluralsight course I used later on in the comments essentially said 'avoid it if you can' (granted, a few years ago).  The general avoidance tactic is to simply throw more starting agents at it, and use targeted test categories.

 The crux of the matter...how badly do you want this?

 So I would suggest that these questions will aid you on your journey:
  • Why do you need (GUI) test automation?  What do you seek to improve?
  • How will you know it has improved?  How will you demonstrate that more (or less) effort is required?
  • Is the team behind this?  How will this effort persist?

 This is what we'll be working towards...I'm sure there will be a report later this year...




Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more