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
Hi, I followed the configuration, watcher works fine if I modify files it adds stuff to the queue but then what? If I manually run the worker, the first few times it seems like it's running the test but it never proceeds? I.e it stays on 1 test if I turn off and turn back on it moved to another one? also the dashboard is not actually showing any of the test results. Also is it possible to define the tester route in a middleware inside web.php?
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Laravel Tests-Watcher - Worker
RUNNING: /usr/bin/script -q /tmp/tw-m9354O vendor/bin/phpunit /home/vagrant/liveandnow/tests/Unit/ResponseTest.php
♥
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Live & Now Tester - Worker
RUNNING: /usr/bin/script -q /tmp/tw-S4f2Xe vendor/bin/phpunit /home/vagrant/liveandnow/tests/Unit/ApiResponseTest.php
vagrant@liveandnow:~/liveandnow$
♥
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Live & Now Tester - Worker
RUNNING: /usr/bin/script -q /tmp/tw-qThe7l vendor/bin/phpunit /home/vagrant/liveandnow/tests/Unit/ResponseTest.php
vagrant@liveandnow:~/liveandnow$
♥
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Live & Now Tester - Worker
RUNNING: /usr/bin/script -q /tmp/tw-YKED20 php artisan dusk /home/vagrant/liveandnow/tests/Browser/LoginTest.php
vagrant@liveandnow:~/liveandnow$
♥
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Live & Now Tester - Worker
RUNNING: /usr/bin/script -q /tmp/tw-PTWgeT php artisan dusk /home/vagrant/liveandnow/tests/Browser/RegisterTest.php
vagrant@liveandnow:~/liveandnow$
[1]+ Stopped php artisan ci:work
vagrant@liveandnow:~/liveandnow$ cd liveandnow
-bash: cd: liveandnow: No such file or directory
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Live & Now Tester - Worker
idle...
♥
vagrant@liveandnow:~/liveandnow$ php artisan ci:work
Live & Now Tester - Worker
idle...
watch:
vagrant@liveandnow:~/liveandnow$ php artisan ci:watch
Live & Now Tester - Watcher
Loading testers...
TESTER: phpunit
TESTER: dusk
TESTER: codeception
TESTER: phpspec
TESTER: behat
TESTER: atoum
TESTER: tester
TESTER: jest
TESTER: react-scripts
TESTER: rake
TESTER: ava
Loading projects and suites...
Project 'PhPUnit'
-- suite 'feature'
-- suite 'unit'
Project 'Dusk'
-- suite 'browser'
EXCLUDED: /home/vagrant/liveandnow/tests/Browser/console/
EXCLUDED: /home/vagrant/liveandnow/tests/Browser/screenshots/
Loading tests...
BOOT: booting watchers...
WATCHING /home/vagrant/liveandnow/app
WATCHING /home/vagrant/liveandnow/tests
WATCHING /home/vagrant/liveandnow/app
WATCHING /home/vagrant/liveandnow/tests/Browser
WATCHING CONFIG: /home/vagrant/liveandnow/config/ci.php
Loading testers...
TESTER: phpunit
TESTER: dusk
TESTER: codeception
TESTER: phpspec
TESTER: behat
TESTER: atoum
TESTER: tester
TESTER: jest
TESTER: react-scripts
TESTER: rake
TESTER: ava
Loading projects and suites...
Project 'PhPUnit'
-- suite 'feature'
-- suite 'unit'
Project 'Dusk'
-- suite 'browser'
EXCLUDED: /home/vagrant/liveandnow/tests/Browser/console/
EXCLUDED: /home/vagrant/liveandnow/tests/Browser/screenshots/
Loading tests...
FILE CHANGED: /home/vagrant/liveandnow/app/Helpers/Parsers.php was modified
QUEUE: adding all tests for the feature suite
QUEUE: adding all tests for the unit suite
QUEUE: adding all tests for the browser suite
The text was updated successfully, but these errors were encountered:
Hi, I followed the configuration, watcher works fine if I modify files it adds stuff to the queue but then what? If I manually run the worker, the first few times it seems like it's running the test but it never proceeds? I.e it stays on 1 test if I turn off and turn back on it moved to another one? also the dashboard is not actually showing any of the test results. Also is it possible to define the tester route in a middleware inside web.php?
watch:
The text was updated successfully, but these errors were encountered: