-
Notifications
You must be signed in to change notification settings - Fork 51
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
[Tracking] Outstanding ActiveRecord 5.2 tests #48
Comments
Thanks for compiling this! I did a quick scan of the tests here, and a few jumped out to me as things that are pretty likely not to work, based on what CockroachDB supports right now:
|
After a few PRs get merged, we'll be down to 60 test files to get through. Thanks to @jordanlewis's tip to skip It can take anywhere from 1 to 4 hours to run a test file, figure out why it's failing, and apply a fix or skip the tests. With 60 outstanding test files, we're looking at between 60 and 240 hours of work. The last 10 files have come in at an hour or less, and if that continues we’ll be closer to 60 hours. To help speed this up a bit, people could quickly scan the tests like @rafiss did (#48 (comment)) and pick out anything that we know isn't going to work with CockroachDB. People are also welcome to jump in and investigate the failing tests. |
I took a rough stab at trying to prioritize the remaining test files. This is very unscientific, but I think it still could be a helpful heuristic to figure out which things to tackle next with our remaining time. I did my best, but it's still quite possible that some of the ones that I've marked as higher priority won't be able to work with CockroachDB, so as always, if you hit a stumbling block, let us know, so we can determine if the test should just be ignored. High priority
Medium priority
Low priority
May not work with cockroachdb
|
I don't have edit permissions on the issue, but |
Sounds good! I was just basing this off of the boxes that are currently unchecked in Ali's issue description above. |
I created individual issues for the outstanding high/medium/low priority test files. I included the failures/errors to make it easier to see what's wrong in the tests. It might make sense to re-prioritize based on the failures/errors. You can find the issues here: https://github.com/cockroachdb/activerecord-cockroachdb-adapter/issues?q=is%3Aissue+is%3Aopen+%5BActiveRecord+5.2+Test+Failure%5D. There are a few test files that are no longer failing, and I didn't create issues for them. It looks like most of the "May not work with cockroachdb" tests don't work with CockroachDB. I didn't create issues for them either. |
Below is a list of all the ActiveRecord tests that get run against PostgreSQL on Rails 5.2. Check off tests once they're passing against master.
There will be tests that don't work against CockroachDB. To skip these tests
test/excludes
that matches the name of the test class if one doesn't already exist. For example to exclude a test fromActiveRecord::AdapterTest
, createtest/excludes/ActiveRecord/AdapterTest.rb
.test_indexes
fromActiveRecord::AdapterTest
:activerecord-cockroachdb-adapter/test/excludes/ActiveRecord/AdapterTest.rb
Line 1 in c3cb637
test/cases
. Everything from the ActiveRecord test suite will be available, so a lot of the excluded test can be copied over. Namespace the test under theCockroachDB
module to avoid name collisions. Seetest/cases/adapter_test.rb
for an example.For information on running tests, see the Contributing guide.
ActiveRecord tests
The text was updated successfully, but these errors were encountered: