Manual testing is used for situations where automated testing does not make sense. This may be due to technical reasons (the application being tested does not have an API that lets tools such as Rapise interact with them) or economic (this part of the application is rarely used and the user interface is changing in each release).
However Rapise can help accelerate and optimize your manual testing as well. Rapise lets you rapidly create manual tests 5x faster than creating them by hand. It integrates with Spira for test management, so you still have a central repository of version-controlled test cases, but Rapise allows you to edit them offline when you have no connection to Spira and also to execute them from within Rapise.
To start manual testing, simply create your test as normal using the New Test dialog box.
For pure manual test you need to select the manual test methodology:
From here you can start creating your new manual test using the Manual Recorder, then edit the created test steps in the Manual Editor. Finally you can save the test to Spira and then play it back using the Manual Playback and Incident Logging screens.
In addition to being used for manual testing, the test step editor lets you view the test steps that define the test scenario so that when you automate the test case, you can easily tie back specific verification points with test steps in Spira.
Finally you can also have the best of manual and automated testing in the same test script, using semi-manual testing. That allows you to automate some of the repetitive tasks in a primarily manual test case.
For a full tutorial using the manual playback, refer to the Exploratory Testing tutorial.
In addition, a working sample of manual testing is available from Spira, simply connect to the sample "Library Information System" project and open the 'Ability to Create New Book (TC2)' test case in the "Functional Tests" folder of the project. That will then display the sample manual test within Rapise: