Over a million developers have joined DZone.

TOTE Model For Testers - Test, Operate, Test, Exit

DZone's Guide to

TOTE Model For Testers - Test, Operate, Test, Exit

Learn to map the TOTE (Test, Operate, Test, Exit) model onto TDD, exploratory testing, design processes, analysis, learning, and more.

· DevOps Zone ·
Free Resource

Is the concept of adopting a continuous everything model a daunting task for your fast moving business? Read this whitepaper to break down and understand one of the key pillars of this model in Continuous Governance: The Guardrails for Continuous Everything.


In 1960, George Miller, presented a model of problem solving which he called the T.O.T.E model:

  • Test, Operate, Test, Exit.

The notion is that you loop around a [Test, Operate]* cycle and when your Test is complete, then you have done enough Operations and you can Exit. It was a model of problem solving, or decision making. I wrote about it a while back on the blog and in my NLP papers

You can find George Miller’s book Plans and the Structure of Behavior on archive.org. He describes the TOTE model in that book.

TOTE in Action

Showing T.O.T.E in action. I drew this dynamically to make the point that it is a cyclical process and we Test to decide if we continue to Operate, to Exit the process, and to change what we will operate.

                                              You can see the 9 second version on Instagram.

We test to build a model, and sometimes we exit because things are Good Enough, but we still need criteria to determine what Good Enough means. Sometimes we operate to learn if something is Good Enough.

TOTE for Learning

At the time that I explored the TOTE model previously, I didn’t make the connection that the arc from Operate -> Test was also a feedback process.

In the TOTE model, the Test learns from Operate, which we can easily map on to Exploratory Testing:

  • We come up with an idea to explore (Test).
  • We explore (Operate).
  • We learn from that (Operate -> Test).
  • We derive new things to explore (Test).
  • Et cetera.

We Exit when our time has finished or when we have covered our ideas or whatever other ‘exit’ criteria we started our testing with.


I’ve also written a lot more code using TDD, and I know that my TDD process very often resembles a TOTE process:

  • Write some @Test code (Test).
  • See if it fails and write some code to make the test pass (Operate).
  • Write more @Test code to flesh out the design (Test).
  • Repeat.

Until our design is complete, or our review of our @Test and code can’t come up with anything new, and we have compared it with our statement of intent, etc.

TOTE Learning

We could view this as a completely well-defined process of evaluation where at every ‘Test’ point we know exactly what we are deciding upon and use the pre-defined evaluation criteria.

We could also view the Operate process as a learning process which feeds into the Test process and explains the cycle. Each time we ‘do’ something (operate), we learn something which we feed into the Test process.

I missed the learning process inherent in the Operate -> Test arc first time around.

I won’t do that again, and that makes TOTE an even better model for the type of work I do.

A model worth investigating.

See Also

Are you looking for greater insight into your software development value stream? Check out this whitepaper: DevOps Performance: The Importance of Measuring Throughput and Stability to see how CloudBees DevOptics can give you the visibility to improve your continuous delivery process.

tote model ,tdd ,software testing ,devops

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}