Alan Richardson's Blog

Subscribe to Alan Richardson's Blog feed
Updated: 7 hours 38 min ago

Promoting Evil Tester Talks Conference Talk and Webinar Archive

Tue, 16/01/2018 - 14:54
TLDR; I have an archive of webinars and talks with extra material bundled as a ‘course’.

I updated my “Evil Tester Talks” Online Talk Archive and realised that I hadn’t actually promoted it through my blog. Too busy creating content and writing talks.

But since I just added two talks and one webinar to the archive, it seemed the right time to promote it.




Find Evil Tester Talks archive online



Exclusive PerformancesOnce I’ve performed a talk, its pretty much over.

  • I tend not to repeat talks, although sentiment and content might get re-used in a busy year
  • The only people who get to see it, are at the conference
Even Live isn’t EnoughThe problem is:

  • I tend to create more material than fits in the talk - so there is some content that no-one sees
  • I cover a lot of stuff in my talks - so people who attend won’t get all of it
  • I do have practical exercises to reinforce messages in the talk, but these only come through when the talk is expanded into a workshop
  • live webinars are often streamed over the phone line and have low-quality audio
An Archive for StudyThe solution I came up with:

  • create an archive of my talks as an ‘online course’
  • upload any live recordings of the talk that I have - after processing them to improve the sound quality
  • create a transcript of the talk
  • upload any bonus material that I created for the talk but which didn’t make it into the talk - usually for time reasons
  • write up the exercises that support the messages in the talk
  • extract the audio into .mp3 style podcast material for easier offline listening
  • upload any practise sessions if the live recording is not available
One Ring to Rule Them AllOriginally my plan was to partition out the talks and content:

  • Evil Tester Talks Technical Testing
  • Evil Tester Talks Automation
  • etc.
But, things don’t seem as easy to partition since a technical testing talk might also cover automating.

So I decided to scrap that idea and uploaded them all into a single course archive.



How to Use?
  • The fact that these were webinars or conference talks mean that they are the perfect length to watch in a lunchtime team meeting.
  • You can then discuss the video and use the exercises to create a knowledge sharing environment and strategy session.
  • Each of the talks can also be used as an individual to improve your process, the exercises are suitable for individual work to create an action plan for your own improvement.
  • You can download the audio mp3’s if you enjoy a podcast format.
  • The slides and transcript are available as pdf to download for faster memory refresh and later personal study.
What does it have?Currently, I’ve uploaded five conference talks and two webinars

  • Push Your Functional Testing Further - March 2016
  • Webinar: Risk Mitigation Using Exploratory and Technical Testing
  • How to Improve your Technical Test Ability - AA Day Poland Keynote
  • Technical Mobile Testing - Eurostar Mobile Deep Dive 2015
  • Automate Or Die - Real World Automation Survival (TestWorksConf 2015)
  • Practical Lessons Learned in Test Automation (Test Automation Day 2015)
  • Webinar: Lessons Learned from Automating - Tabara Webinar 2016
Only two of these (Risk Mitigation, AA Day Poland Keynote) are available online elsewhere.

I’ve tidied up the audio, editing, added transcripts and included bonus material for all of them. So even if you’ve seen those two already there are still 5 new talks for you.

Current pricing $10. Yeah I know. Too cheap. I’ll remember to increase the price later when I add more stuff.

And once, you’ve bought in, you’ll get access to any talks I add to this archive for free.

What will it have?I’ll be going through my archive of recordings and material and uploading most of the stuff that I have, but can’t say for sure when I’ll upload them or exactly what content I’ll include.

I can’t guarantee that it will have every talk I ever create or have created, I might decide to repartition it if it starts to become overly large and unwieldy as a single archive. But I do plan to make every archive OTT in terms of value for money.

Why?
  • I think archives are useful.
  • I already have the material I should release it.
  • Having a transcript allows me to repurpose it into written form later.
  • Having a transcript makes it easier for me to review my past talks that didn’t make it into blog form.
I think its a win-win. I gain by revisiting the material. I think you will gain by watching the material and following the exercises, enough to charge a nominal fee for access.

Where?

More details about the Evil Tester Talks archive are available online.

Categories: Agile, Software Testing

Testability vs Automatability - in theory (Free Bonus Video Inside)

Fri, 12/01/2018 - 16:38
TLDR; Testability is for humans. Automatability (Automatizability) is for applications.

I was doing some research for my upcoming Eurostar webinar and I encountered a few videos and posts of people who were using ‘testability’ to refer to the ability for the application to support automated execution.

I didn’t think that was appropriate. I’d rather distinguish between Testability and Automatizability. The more popular form of Automatizability seems to be Automatability.



When we look at application features associated with testability we may find overlap with the application features we associate with automatizability. But humans can often work with a less formal implementation. What works for humans does not always work for other applications that want to automate your application.

I’m mainly concentrating on application support for testability here, rather than: development process testability, infrastructure testability, test ability.

But I do also touch upon technology testability.

TestabilityBasically - If we can test an application then we can consider it testable.

We can increase our ability to test an application by using tools and understanding the technology.

Some technologies seem easier to test than others, they have a higher intrinsic testability.

  • This is a subjective assessment.
  • I find a web app more testable than a mobile app or a green screen app.
    • more tools support my testing of the web technology and mobile technology
    • ergonomics and usability of the web technology are easier for me to test than the mobile app
    • etc.
We can increase the testability of an application by adding features to help us test it more easily.

  • This makes the application more testable.
  • Some of the features might help usability.
Testability is not Automatizability
  • Testability - does the application have features that make it easier for a human to test?
  • Automatizability (Automatability) - does the application have features that make it easier to control and interrogate by another application.
The features we add to make it more testable are not necessarily the same features that we add to make it more automatable.

e.g. logging

  • Improved testability by logging that shows hard to observe messages or internal state transitions or variables
  • the logging might improve Automatizability if it is easy to parse and accessible by another program
Testability is not Free - consider riskThe features we add might come with Risks.

  • It might impact Usability if it clutters the screen or confuses the user so the user needs to be able to choose if they see it or not
  • It might impact security if it gives away too much information so we need to be able to switch it off the ability to see it for specific users, or environments
  • It might impact performance, so we might need to only have it run on specific environments
More resourcesTestability is a broad subject and I’m really only concentrating on features we can add to applications to make them more testable here.

If you want to explore testability in more detail then consider:

Summary
  • Testability is not Automatizability (Automatability)
    • Testability relates to Human interaction
    • Automatizability relates to application interaction
  • Some technologies are more testable than others because of tool support and usability
  • Application testability can be increased by adding specific features to support testing
  • Testability features might overlap Automatizability features
  • Application automatizability supports programmable observation, interrogation and manipulation
Video
Categories: Agile, Software Testing