-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get automated tests working #27
Comments
Definitely agreed! This is my current priority. Tests are mostly running (manually) at this time, and I'm working on the few exceptions that seem to stop backdrop in its tracks that didn't stop d7 tests from completing their run. Not 100% sure what changed there yet but here we are. There are quite a few failures to take a look at if you're motivated to run them yourself, but I will have time to get to them next week. 90% of them are in "checkout" and I think it might be a problem with the way the tests were written versus what backdrop is doing now, but i'm not 100% sure about this either without diving in. I'm planning to wait to set up github actions to run the tests automatically until we're at a baseline state of "tests are passing", because just having every PR fail a bunch of tests unrelated to their changes is, imho, super obnoxious. |
Sounds good. Does the current dev version contain the latest versions of the tests you've been tweaking? I may take a look at some point this week. |
Yes, dev is up to date what i'm currently working with and i'll make an effort this week to keep it pretty up to date as I fix bits and pieces of the tests. |
Well, i've done exactly what I said I wouldn't by accident! Functional tests are running, there are 0 fails, but there are some exceptions right now stopping them from all passing. I wasn't getting any exceptions on my local, so there is at least one test there I need to look further into. Most of these are related to I ended up commenting out two tests that I just really couldn't figure out, and created an issue to follow up on those because the feature is also actually broken: #29 I also deleted a test related to |
In porting complex modules (like OG, which I helped port), I have found that porting tests sooner rather than later is highly beneficial, as you'll find bugs you have missed.
The text was updated successfully, but these errors were encountered: