Modelling

TLDR; Often the process of modelling is more important than the models, we carry forward what we learn rather than remodel consistently.

I was looking through old folders of notes to feed to the shredder and paused to comment on some graphical models prior to the shred.

TLDR; Updated code for Selenium WebDriver Course for WebDriver v4 free online and released Open Source Profile conference video for free.

TLDR: Every time we test something we are testing from models. Modelling is a key skill for Software Testers. Errors cannot be identified without a model to compare them. Quality Control cannot be conducted without a model.

The most common Testing Entities that I’ve encountered over the years are: Test Condition, Test Scenario, Test Case, Test Script. In my Testing I pretty much now have: Test Idea, Test Log (Execution Log). Is there any value in the original Testing Entities? There might be if we view them as logical concepts, but not really as physical artifacts.

Wherein the TOTE (Test Operate Test Exit) model is used to explore the nature of feedback and abstraction of test phases and map the TOTE model on to TDD, Exploratory Testing, Design processes, Analysis, Learning, Decision Making and Problem Solving.

TLDR; Variation in testing often leds us to test data, flows and environments. We can increase the chance that we learn something relevant by reading more blogs, watching YouTube and attending conferences. We can also trigger insights, that we ourselves have gained, by reading meaning into unrelated text, content or koans.

TLDR; An example of modelling the application flow of a simple functionality. Modelling helps think through coverage and test ideas and think about what next for your testing.

I chose the very simple I Feel Lucky functionality on Google to use as an example application for modelling to support exploratory testing. I recorded the modelling session and explained my thought processes as I went.

Path Analysis for Software Testing

TLDR; This essay explores the use of graph models in testing and the practice of structural path derivation using 3 coverage concerns: node coverage, link coverage and loop coverage. Predicate coverage is considered but is not covered in detail. An exploration of, and notes on, model path analysis for testing: