bin/rails test:system result differs

[naofumi-fujii]

sample app is https://github.com/naofumi-fujii/my-sample-rails/pull/1/files

without test-unit-rails

[naofumi.fujii]$ ./bin/rails test:system
Run options: --seed 37010

# Running:

Puma starting in single mode...
* Version 3.9.1 (ruby 2.3.3-p222), codename: Private Caller
* Min threads: 0, max threads: 1
* Environment: test
* Listening on tcp://0.0.0.0:51871
Use Ctrl-C to stop
.

Finished in 2.432139s, 0.4112 runs/s, 0.4112 assertions/s.
1 runs, 1 assertions, 0 failures, 0 errors, 0 skips

with test-unit-rails

[naofumi.fujii]$ ./bin/rails test:system
Run options: --seed 14897

# Running:



Finished in 0.000571s, 0.0000 runs/s, 0.0000 assertions/s.
0 runs, 0 assertions, 0 failures, 0 errors, 0 skips

[kou]

It may be fixed by adding test:system to https://github.com/test-unit/test-unit-rails/blob/master/lib/test/unit/rails/testing.rake .
Would you try to fix it?

[naofumi-fujii]

sure!

[naofumi-fujii]

PRed at #17 !

[naofumi-fujii]

with #17

[naofumi.fujii]$ ./bin/rails test:system
Loaded suite system
Started
Puma starting in single mode...
* Version 3.9.1 (ruby 2.3.3-p222), codename: Private Caller
* Min threads: 0, max threads: 1
* Environment: test
* Listening on tcp://0.0.0.0:51684
Use Ctrl-C to stop
.

Finished in 2.658045 seconds.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 tests, 0 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0.38 tests/s, 0.00 assertions/s