Hello. We've met somehow the situation similar to #615. It counts the amount of tested resource differently with serial and parallel running. It also generates the wrong coverage report with parallel running. I've created a dedicated branch with a reproducible state https://github.com/innogames/puppet-clickhouse/tree/parallel_rspec
To reproduce:
git clone -b parallel_rspec https://github.com/innogames/puppet-clickhouse
cd puppet-clickhouse
pdk test unit
pdk test unit --parallel
pdk test output
$ pdk test unit
pdk (INFO): Using Ruby 2.4.4
pdk (INFO): Using Puppet 5.5.6
[✔] Preparing to run the unit tests.
[✔] Running unit tests.
Evaluated 46 tests in 2.531676031 seconds: 0 failures, 0 pending.
Total resources: 16
Touched resources: 16
Resource coverage: 100.00%
$ pdk test unit --parallel
pdk (INFO): Using Ruby 2.4.4
pdk (INFO): Using Puppet 5.5.6
[✔] Preparing to run the unit tests.
[✔] Running unit tests in parallel.
Evaluated 46 tests in 6.10995585 seconds: 1 failures, 0 pending.
Total resources: 18
Touched resources: 17
Resource coverage: 94.44%
Untouched resources:
Class[Clickhouse]
Hello. We've met somehow the situation similar to #615. It counts the amount of tested resource differently with serial and parallel running. It also generates the wrong coverage report with parallel running. I've created a dedicated branch with a reproducible state https://github.com/innogames/puppet-clickhouse/tree/parallel_rspec
To reproduce:
pdk test output
My Gemfile.lock
pdk version is 1.7.1