Closed possibly closed 9 years ago
Dug deeper into the issue, + some fixes on my local fork, and fixed this issue. The new problem is in this log. Probably some print statements should pin point the issue, but for some reason the tests are not locating elements on the page.
HOLY MOLY THIS IS NEVER ENDING. I seriously cant figure out why my tests work flawlessly on my local machine but Selenium fails to "locate element" on Travis. Still working on this...
Finally fixed this! Woo! The problem was in the try/catch block I had in my test...so much pain for so little gain.
woohoo! @possibly is stomping bugs/issues today!
Base Fork (our repo) <-- Merging Fork Travis CI detects a new merge request, off to go test! My travisCI code, at one point, does "sudo git clone https://github.com/possibly/ccsf_coders_website.git /var/www" This clones the repo, WITHOUT THE MERGED FORK, and tests against THE OLD STUFF WE ALREADY KNOW PASSES!
How do we get TravisCI to pull the Merge Request, not the Base Fork?