TestOptimal provides 5 ways to generate test sequences and execute them automatically against your web applications. Each option has its own merits in testing different aspects of your applications.

• RandomSequencer
  RandomSequencer generates the test sequence by randomly selecting a transition from the current state. You can set conditions when to stop the test execution.
  
• GreedySequencer
  GreedySequencer works the same way as RandomSequencer except that it prefers un-traversed (un-tested) transitions over already traversed transitions. This helps to achieve the desired coverage with less number of test steps.
  
• OptimalSequencer
  OptimalSequencer uses the proven optimization algorithms to generate the optimal test sequence to achieve 100% coverage of your application. Because only the minimum number of test steps have to be repeated, the test execution completes in least amount of time.
  
• mCaseOptimal
  mCaseOptimal generates the optimal test sequences to cover all states and transitions contained in mCases. Use mCaseSequencer if you just want to test certain scenarios or parts of your application.
  You may also use mCaseOptimal with virtual users to simulate concurrent users running certain test scenarios.
  mCase can be created and removed easily. It allows you quickly create test cases to test parts of the application.
  
• mCaseSerial
  mCaseSerial is a variation from mCaseOptimal. It differs from mCaseOptimal by preserving the order of transitions/states in mCase(s) in the test sequences it generates.