Skip to main content

Update on the test automation framework

About a year ago I started harping on the test automation bandwagon, and had introduced basic smoketests & New Relic Synthetics 'scripted browser' monitors (both Selenium-based).  In the spring of 2016 I used the Pluralsight course '' to help build our inaugural UI test framework.  I wrote out a number of smoketests and 'hey this bit us on the last deploy, let's write a test for it', and the idea quickly proved itself.  Very shortly afterward we hired a QA guy specifically for automation experience, and now...

  • He took the framework to a whole new level, and it's now the defacto way forward for QA
  • More QA folk were hired, and they are now learning to use the framework to write mundane tests
  • Some QA folk initially were 100% in the camp of 'QAs do not write code, ever' - and now they are pushing themselves forward - learning not just our UI framework, but learning API testing as well!
  • The initial QA automation hire (who continues to be awesome and an inspiration) has also written an API test framework in a similar vein, and we're now starting to adopt that as 'how we test APIs'
  • The future is very exciting for us, and more and more 'high business value' things are coming down the line...
This is a very brief success story, but wanted to share for those stuck in 'this is impossible'-land.

Our path to software quality started only a year ago with...
  1. Zero QA staff, little monitoring
  2. Some QA staff, but not interested in automation, very basic monitoring
  3. Semi-automated smoketests and scripted monitors
  4. A UI test automation framework borne from a month of evenings/weekends and a Pluralsight course (zero experience)
  5. A functional and useful framework taken to the next level by a QA automation hire
  6. More and more interest in QA to join the automation crew
  7. API testing using SoapUI
  8. API test framework that will leverage Postman code generation
  9. Investigation into Cucumber/SpecFlow...

You won't know until you try...

P.S.  I should note that much of this is 'after the fact' software quality.  In hindsight it might have been more effective to push harder on centralized logging/metrics (which is now also a thing, and super amazing).  You should also note that people made this successful.  :)


Popular posts from this blog

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 configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally 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$\\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-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…