Back to Basics; capiche?

This ZD|Net article's right on. Navigating the frequent and massive Windows 10 Updates is simply "burdensome". And the new features aren't that compelling. Time to re-think the strategy, MSFT!

Another interesting insight from the article, "it's widely known that Microsoft let go a bunch of its Windows testers back in 2014, substituting flighting and new unit testing procedures in their stead. I don't think Microsoft will reverse this course and bring back testing as a separate discipline. But they could improve their testing procedures and supporting infrastructure as part of a return to a focus on fundamentals."

I've worked at large companies that effectively eliminated QA engineers on behalf of "Agile Stretch". It generally doesn't work well! Developers have a different mindset and focus than Testers, and the end quality often reflects that. You really don't want to go there! 😮

Installing Robot Framework on a MacBook

I recently faced challenges getting the open source Robot Framework to work on my MacBook, which is running OS X El Capitan. In general, the installation process should be trivial, but here's what finally worked:

1. If you have the brew package manager installed, update it:
   
       brew update
   
2. Use brew to install (or upgrade) the chromedriver program:
   
     brew upgrade chromedriver
   
3. Make and use a Python virtualenv for the framework installation:
   
     pip install --upgrade virtualenv
     source virtualenvwrapper.sh  # Note: Depends on where virtualenvwrapper.sh was installed to.
     mkvirtualenv robotframework
     workon robotframework
     cdvirtualenv
4. Install the necessary framework packages:
   
     pip install --upgrade robotframework
     pip install --upgrade robotframework-selenium2library
     pip install --upgrade requests

Now, you'll be able to use the robot command to run test scripts OK :-)

Integrated or Independent QA?

A friend at work forwarded this article to me after a lunch time discussion about QA testing, and whether it should be integrated within the development team activities or operate as an independent effort.

The author's viewpoint is that there is value in a separate team and effort.

I think there’s a parallel to scientific method, too, which makes QA as a separate process valuable. Review by a different team, that corroborates readiness through their own effort, is important for overall confidence, too. Not to say that’s infallible, but it demonstrates an important watermark.

JMeter - A very handy tool

I suppose some techies will laff when they read this, but I'm getting a first-time intro to JMeter and it's COOL! It's an open source tool, from Apache, which allows the test engineer to codify HTTP and other protocol requests, issue them to a test server, save the responses, and validate them vs. one or more assertions. Since it's written in Java, it runs on Windows or Linux nicely, too.

The UI is a little clunky and you have to make sure to Save your configuration changes before starting a run (it doesn't prompt you to do so), but it provides a lot of testing capability and flexibility.

Testing Priorities for the new Web

In case it isn't already obvious, the future is Now. Web 2.0 is running in production at many sites; it's no longer sequestered just in research labs and academia.

Because of the increasing collaboration, social, and mash-up (uh, "syndication") features of Web 2.0, I think the following testing categories will gain in importance:

+ Performance (particularly scaling)
+ Security
+ Privacy

These categories will probably remain "about the same":

= Functionality
= Ease of Use
= Test automation

And finally, my intuition tells me that these categories will be "less emphasized":

- Cross-platform
- Multi-browser support
- Exhaustive test coverage