`assert_api_conform` method does not perform actual assertions, causing a warning for Rails >= 7.2

[schwarzfa]

Description

The provided assert_api_conform method does not perform actual assertions using Rails' testing framework. As a result, when this method is used in Rails tests, Rails emits a warning indicating that the test case does not perform any assertions.

Before Rails 7.2 you could configure Rails to ignore or only log such warnings (:ignore being the default):

config.active_support.assertionless_tests_behavior = :ignore
config.active_support.assertionless_tests_behavior = :log

With Rails 7.2, the ActiveSupport::TestCase emits warnings when tests are executed without any assertions, with no more way to configure the behavior.

Steps to Reproduce

1. Set Up a Rails Test Case in a Rails app with version >= 7.2

require 'test_helper'

class ApiConformanceTest < ActiveSupport::TestCase
  test "API response conforms to specification" do
    get '/api/endpoint'
    assert_api_conform(status: 200)
  end
end

2. Run the Tests:

rails test

3. Observe the Warning:

Test is missing assertions: `test_API_response_conforms_to_specification` /path/to/test

Thank you for having a look and maintaining this great gem :)

[ahx]

Hey @schwarzfa. That's right currently assert_api_conform does not know anything about the used testing framework, but just throws an exception (with a hopefully useful error message).

I am mostly not using Rails, that's why there is no close integration part of the gem, but I would like to improve the story with Rails. I was also thinking about some sort of test integration for various frameworks. Maybe we can take this issue as a starting point to do that.
Do you have a specific API in mind?

How about this:
When including OpenapiFirst::Test::Methods in your test, it tries to detect what testing framework the current class is using and calls the respective assert methods / matchers? – One thing I like about this is that the current API does not change and you can do things just as described in the Readme. One disadvantage of this might be that just calling assert_api_conform is not idiomatic for the used testing framework. For example, in rspec one would expect something like expect(thing).to match_something.. But I think that would be okay.

Any thoughts about that?

Thank you for the report and your feedback!

[ahx]

This should be fixed with 2.2.1