8000 cleanup support for Rails 2.3 and remove old integration tests by kares · Pull Request #280 · jruby/jruby-rack · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

cleanup support for Rails 2.3 and remove old integration tests #280

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

Merged
merged 4 commits into from
Jun 1, 2025

Conversation

kares
Copy link
Member
@kares kares commented May 30, 2025

mostly just removing unused code/specs

@chadlwilson
Copy link
Contributor

I must admit that I didn’t understand this stuff, however I wondered whether rather than deleting it, it needed to be adapted to rails 6.1 and 7.x to actually run specific rails tests there - which is why I didn’t delete them earlier.

There seemed to be some magic there that looked for these specs if they existed for a given rails version and run them. I somehow had the impression that there were not real tests being run via the appraisals for later versions without such version specific dirs.

But yes, these are definitely unused right now.

@kares
Copy link
Member Author
kares commented May 30, 2025

I must admit that I didn’t understand this stuff, however I wondered whether rather than deleting it, it needed to be adapted to rails 6.1 and 7.x to actually run specific rails tests there

As long as we're talking about the Rails booter specs then than would depend on whether there's changes to the stuff we're adding/overriding.

There's 2 groups (similar to the removed 2.3 group) left here:

describe "Rails 3.x", :lib => :stub do and describe "Rails 3.1", :lib => [ :stub ] do so I think the names are not that great anymore (should be pretty much one Rails group or just flat specs with better descriptions).

The idea around :lib => :stub is we test stubbed regardless of what actual Rails APIs we run.

There seemed to be some magic there that looked for these specs if they existed for a given rails version and run them.

The integration spec mostly has those and there the removed group having :lib => :rails23 meant that pretty much never run. Same logic as before would apply, if we want to test something specific that changes in a given Rails version (against an actual Rails API), than it would be tagged like that.

@kares
Copy link
Member Author
kares commented May 30, 2025

Now having a second look, you're right.

We should have some Rails skeleteon under src/spec/stub based on actual Rails version and use those as a (smoke) "integration" test. And I should also do more cleanup here, since I obviously missed a lot 😜.

@kares kares changed the title cleanup support for Rails 2.3 cleanup support for Rails 2.3 and 3.0 tests May 30, 2025
@kares kares changed the title cleanup support for Rails 2.3 and 3.0 tests cleanup support for Rails 2.3 and 3.x tests May 30, 2025
@kares
Copy link
Member Author
kares commented Jun 1, 2025

Managed to remove the Rails stub apps, and also looked into adding back (in a follow-up PR) some based on the Rails versions currently supported.

I have a 7.2 passing tests locally and will setup another one likely for Rails 6.1 (Rails.logger defaults changed between 6 -> 7, so it's worth testing). Unfortunately there seems to be issues matching the appropriate lib: railsXY during a run.

@kares kares changed the title cleanup support for Rails 2.3 and 3.x tests cleanup support for Rails 2.3 and remove old integration tests Jun 1, 2025
@kares kares merged commit 210cbbc into jruby:master Jun 1, 2025
61 checks passed
@kares kares deleted the for-1.3 branch June 1, 2025 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0