Those that generate a report after all tests are complete.
Example of 1:
A presenter which a developer runs in the console. The developer would like to see when a step starts executing, and what the result is as it has finished, or the errors it generates. Otherwise, if it's presented after the fact, then if a step takes a long time or hangs, the developer won't know what step that was.
Example of 2:
An HTML report, or an XML report.
We can call them RealTimePresenter and ReportPresenter.
I imagine there are two types of presenters:
Example of 1: A presenter which a developer runs in the console. The developer would like to see when a step starts executing, and what the result is as it has finished, or the errors it generates. Otherwise, if it's presented after the fact, then if a step takes a long time or hangs, the developer won't know what step that was.
Example of 2: An HTML report, or an XML report.
We can call them RealTimePresenter and ReportPresenter.