Test execution

Needs compilation prior to execution

YES

NO

Test invocation

- connect to DB
- call API to execute package or suite

execute "rspec" from command prompt in project root

Default tests execution scope

NONE
You need to explicitly state either a suite or a package to be tested'

All test for project
By default, calling "rspec" command from project root will exeute all tests for project

Parallel test executiuon

Doable - do it yourself.
By splitting test into separate suites and running them from CI in parallel jobs.

YES-automatic
with open-source libraries

Transaction management

Manual

Automatic
Conforms with RSpec standard for keeping the object(s) unchanged outside of test scope

Test setup/cleanup

One mandatory setup and cleanup per test package.
(Bolierplate code when not used)
Useless when different setup needed for each test.

Optional multiple setups cleanups can be defined on each level of example group.
Two triggering modes can be mixed for setup/cleanup:
- Before all tests in example group
- Before each example group
Setups /cleanups available for entire suite (before suite/after suite)
Setups /cleanups can be invoked with filtering by tags too