You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is similar to issue #19, only the database cleanup does not occur only when the tests fail when running the command 'rake protractor:spec_and_cleanup'. I am running protractor-rails 0.0.15. Ruby version 2.1.5.
This is my final outputs from a failed test:
...
[2015-05-22 10:32:17] INFO going to shutdown ...
[2015-05-22 10:32:17] INFO WEBrick::HTTPServer#start done.
Exiting
kill left over selenium processes...
Selenium Standalone has exited with code null
This is my final outputs from a passed test:
[2015-05-22 10:39:09] INFO going to shutdown ...
[2015-05-22 10:39:09] INFO WEBrick::HTTPServer#start done.
Exiting
kill left over selenium processes...
Selenium Standalone has exited with code null
rake db:test:prepare to cleanup for the next test session
** Invoke db:test:prepare (first_time)
...etc
The text was updated successfully, but these errors were encountered:
This is similar to issue #19, only the database cleanup does not occur only when the tests fail when running the command 'rake protractor:spec_and_cleanup'. I am running protractor-rails 0.0.15. Ruby version 2.1.5.
This is my final outputs from a failed test:
...
[2015-05-22 10:32:17] INFO going to shutdown ...
[2015-05-22 10:32:17] INFO WEBrick::HTTPServer#start done.
Exiting
kill left over selenium processes...
Selenium Standalone has exited with code null
This is my final outputs from a passed test:
[2015-05-22 10:39:09] INFO going to shutdown ...
[2015-05-22 10:39:09] INFO WEBrick::HTTPServer#start done.
Exiting
kill left over selenium processes...
Selenium Standalone has exited with code null
rake db:test:prepare to cleanup for the next test session
** Invoke db:test:prepare (first_time)
...etc
The text was updated successfully, but these errors were encountered: