O forum atual do agile testers está sendo depreciado, ou seja, não é possível criar ou responder a threads no momento. Por favor utilize o novo fórum https://github.com/AgileTesters/forum/issues

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

Topic created · 1 Posts · 365 Visualizações
  • TLDR; Map the TOTE (Test, Operate, Test, Exit) model on to TDD, Exploratory Testing, Design processes, Analysis, Learning, Decision Making and Problem Solving.


    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 being 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

    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. And 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 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)
    • etc.

    And we Exit when our time has finished or 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 fail and write some code to make the test pass (Operate)
    • write more @Test code to flesh out the design (Test)
    • and 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.

    A post shared by Software Testing Tips & Videos (@eviltester) on <time datetime=“2017-05-03T06:14:42+00:00” style=“font-family: Arial,sans-serif; font-size: 14px; line-height: 17px;”>May 2, 2017 at 11:14pm PDT</time>

    See also

    PS. If you want your own T.O.T.E model diagram then feed this into Graphviz or WebGraphviz

    digraph G {   node [shape = "rectangle"];  Test -> {Operate Exit}  Operate -> Test  subgraph { rank = same; Test; Exit}  Exit [shape = "ellipse"];}

    Leia mais em http://blog.eviltester.com/2017/05/tote-model-for-testers-test-operate.html