Skip to main content

TALMUG: Agile testing

Been a while since I posted anything - so busy with life and work.

Last night I had the chance to attend the Toronto Application Lifecycle Management User Group (TALMUG) as they were discussing something I've been grappling with:  Testing (specifically, Agile testing)

Some key points I pulled out of the discussion:

  • The key to doing Agile correctly is 'definition of done' and retrospectives (continuous improvement)
  • The key to ensuring testing is a part of the process is 'definition of done', and thus, you must have some sort of Agile-y development process
  • The key to getting the time to continuously improve is to PARTNER with your business colleagues - IT must be viewed as a partner, not a cost centre or necessary evil or code factory
  • The key to transforming to a 'team is responsible for all vs. I'm only responsible for my part' is holding the entire team accountable - no deadline extensions, public shaming
    • Sub-key is 'attitude is king' - a team with the right attitude can accomplish anything
  • If you find not enough time to test - most likely committed to too much up front
  • Test automation is best done in TINY pieces.  For example:
    • A login sequence (load page, enter user, enter pass, click login) is too long!
    • Have code for 'load page', 'enter user', 'enter pass', 'click login'
    • This means you can substitute user/pass, or one or the other, for stuff like different environments, or negative testing
  • Test automation requires consistent and agreed-upon naming of IDs that CANNOT change.
    • This gives you a much longer shelf life for UI-based tests
  • Test automation 'helper' tools are useful for starting out, but generally fall down in long-term maintenance
    • That said, they are a good 'better than nothing' first step
  • MOST IMPORTANT I thought was being able to tell a story using metrics
    • Quality is end to end, right? (build quality in)  So use a variety of metrics across the process flow to determine if quality is improving or not
    • Start measuring right away - even if the measurements are manual
It was great - many thanks to ObjectSharp for hosting the event!


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…