Is “Coded UI” automation dead?

Visual Studio Enterprise provides Coded UI software test automation with several object oriented languages available for scripting.  Recovery scenarios are available with Try/Catch constructs and Verification points through assertion checks.  The “Test Builder” performs object inspections to view searchable object attributes of your target under test.  It will also record interactions with your target under test (which does not have to be a VS project) but I recommend these recordings are used for learning only.  Data sources are available for looping through data driven parameterized tests.  Your tests can be run from the VS Test menu or can be executed from command line on non-VS Enterprise machines using the generated DLL.  Seems like a fairly full functioning test environment if your organization has already invested in MSDN or VS Enterprise licenses. So no, Coded UI automation is not dead and remains an option for your test automation needs!

Testers Anonymous

** no intended blasphemy or negative regard to anyone associated in any way with AA

As software testers we often have negative views of our jobs and ourselves from our collective experiences over the years seeing schedules shortened and our work minimized.  Actually we have great opportunity to positively impact our products and the lives of our customers.  To start viewing our jobs and ourselves differently, I am proposing these first steps of Testers Anonymous:

  1. We admitted we were powerless over our current software test and release – that our process has become unreliable.

Many test and release engineers and managers have a hard time admitting that they can’t control their software promotion, test, and release. Once they acknowledge that they are unable to stop defects on their own, the recovery process can begin.

  1. We came to believe that a power greater than ourselves and current methods could restore us to sanity.

Believe that people and teams with externally released severe defects need to look to something greater than their current methods. Those working the steps are free to choose whatever higher power works for them but normally more structure and process is recommended over reduced methods.

  1. Make an inventory of our process, escapes, tools, and documents.

This step requires self-examination that can be uncomfortable, but honesty is essential in this process. The key is to identify any areas of past regret, frustration, and inefficiency as well as areas of success. Survey all team members for inputs in all areas.

4. Admit to Management, to ourselves, and to our teams being the exact nature of our wrongs and our plans to improve.

This step involves admitting to past poor results. Often, all will share the most important issues and successes they wrote down during the survey.

Start a local Testers Anonymous support group and help others on the path to recovery.

Software Test and Release issues in the news

It has not been a good week for the public image of companies being in control of handling software test and release issues.  A sampling of the last week:

Samsung Galaxy S8 won’t work on wifi – called minor and limited area in this article but other reports say it is more prevalent to all locations.  A fix is said to be available.

Tesla loses top safety rating by Consumer Reports – the inability to deliver the automatic braking feature is why consumer reports lowered rating.  Fixing other issues (recalled 53,000 Model S and Model X vehicles to fix an unrelated parking brake issue) has lead to inability to deliver features for Tesla.

F-35’s Cost Could Rise by $1Billion Because of Extra Testing – this is not all software testing costs, but extra flight testing because of software issues is major factor.

Feel free to share me stories of good news of how you have taken control of your software test and release!

Mobile test strategies

Best practices for implementing a mobile test strategy by George Lawton

Positive summarized points:  Prioritize functions most important to your end users. Using an optimal mix of devices in testing that vary by location, type of device, OS version, configuration and connectivity options (KLOMAR = #2 Test plans using Customer Configurations).  Have a test automation framework implementing common functions and services for your product and system to simplify future test automation.  Apply a system wide focus.