Andrew Cooke | Contents | Latest | RSS | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

[Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life; [Link, Bike] Cheap Cycling Jerseys; [Link, Music] Music To Steal 2017; [Link, Future] Simulated Brain Drives Robot; [Link, Computing] Learned Index Structures; Solo Air Equalization; Update: Higher Pressures; Psychology; [Bike] Exercise And Fuel; Continental Race King 2.2; Removing Lowers; Mnesiacs; [Maths, Link] Dividing By Zero; [Book, Review] Ray Monk - Ludwig Wittgenstein: The Duty Of Genius; [Link, Bike, Computing] Evolving Lacing Patterns; [Jam] Strawberry and Orange Jam; [Chile, Privacy] Biometric Check During Mail Delivery; [Link, Chile, Spanish] Article on the Chilean Drought; [Bike] Extended Gear Ratios, Shimano XT M8000 (24/36 Chainring); [Link, Politics, USA] The Future Of American Democracy; Mass Hysteria; [Review, Books, Links] Kazuo Ishiguro - Never Let Me Go; [Link, Books] David Mitchell's Favourite Japanese Fiction; [Link, Bike] Rear Suspension Geometry; [Link, Cycling, Art] Strava Artwork; [Link, Computing] Useful gcc flags; [Link] Voynich Manuscript Decoded; [Bike] Notes on Servicing Suspension Forks; [Links, Computing] Snap, Flatpack, Appimage; [Link, Computing] Oracle is leaving Java (to die); [Link, Politics] Cubans + Ultrasonics; [Book, Link] Laurent Binet; VirtualBox; [Book, Link] No One's Ways; [Link] The Biggest Problem For Cyclists Is Bad Driving; [Computing] Doxygen, Sphinx, Breathe; [Admin] Brokw Recent Permalinks; [Bike, Chile] Buying Bearings in Santiago; [Computing, Opensuse] Upgrading to 42.3; [Link, Physics] First Support for a Physics Theory of Life; [Link, Bike] Peruvian Frame Maker; [Link] Awesome Game Theory Tit-For-Tat Thing; [Food, Review] La Fabbrica - Good Italian Food In Santiago; [Link, Programming] MySQL UTF8 Broken; [Link, Books] Latin American Authors

© 2006-2017 Andrew Cooke (site) / post authors (content).

Simple Schema for Describing Tests

From: "andrew cooke" <andrew@...>

Date: Mon, 1 Jan 2007 21:43:24 -0300 (CLST)

I've been meaning to write some notes about tests for a while now.
Unfortunately I keep thinking of different things, and then forgetting
them.  So I will probably add more comments here over time.

But my main idea, which I don't expect to change, is that there's a lot of
confusion about tests because they can be viewed in several different
ways, and terminology associated with testing is often associated with a
particular viewpoint.  Worse, sometimes the same terminology means
different things depending on the viewpoint chose.

The three viewpoints I currently have on my list (entries to this list are
some of the things I keep forgetting) are:
- Extent
- Support
- Process

The EXTENT of a test can vary from a single class to a whole system.  A
common intermediate point is to test all related code for a single layer
or language (for example, testing Java code with mocks for the database,
user input, etc).

By SUPPORT I mean the infrastructure used to perform the tests.  JUnit,
for example, or Fitnesse.  Those two show how support can be related both
to extent (JUnit was originally intended for unit tests - single classes)
and process (Fitnesse was originally intended for acceptance tests).

Tests occur within the development PROCESS (whether it's explicit or
not!).  This is related to the "aim" of the test - whether it is for
developers to be check their code, make contracts explicit, or integrate
classes, or for customers to decide whether the product meets their
requirements.

Let's take some examples:

Unit tests
- extent is a single class (well, sometimes a handful...)
- support is FooUnit (depending on the langauage)
- process is development (guiding implementation, making contracts explicit)

Regression tests
- extent is typically a single test, but may extend to a complex system
- support is likely FooUnit plus an automated build
- process is development/test (tickling bugs, fixing them, and making
  sure they stay fixed)

Acceptance tests
- extent is usually the whole system (or as large a portion as possible)
- support may be Fitnesse and/or GUI test tools
- process is customer acceptance

In practice, of course, every project is different and should be tested
appropriately.  What I am trying to do here is not give a fixed set of
tests, but provide a framework within which we can describe "what we are
doing", so that everyone is on the same page.  My hope is that
focussing(*) extent, support and process makes that easier - rather than
say "do unit tests" we should be saying "do tests with extent X and
support Y for process Z".

Andrew

(*) Is there some way to make Firefox use British spelling when it checks?
 My OED says that focussing is perfectly OK!

Another Test Example

From: "andrew cooke" <andrew@...>

Date: Tue, 2 Jan 2007 10:38:21 -0300 (CLST)

Here's another example.  I am writing integration tests for a web
application using Spring's MVC.  Since I'm using Spring I can do this from
within Java, using the AbstractTransactionalDataSourceSpringContextTests
class, which extends JUnit.

So the extent of the classes is pretty much the whole system, the process
is integration testing (making sure everything works together), and the
technology is Spring/JUnit.

I think this is a good example, because the technology includes JUnit,
which means that someone is going to refer to these as "unit tests". 
That's the kind of confusion that arises from not specifying clearly the
extent/process (and it's easy to see why it happens - when you're
surrounded by the details of programming it's easy to lose site of the
"big picture").

Andrew

Comment on this post