example workflow
Update ruby.yml
limit builds
Update ruby.yml
postgres service
Update ruby.yml
pg_port
copy config files
Update ruby.yml
Update ruby.yml
Update database_travis.yml
Update ruby.yml
Update ruby.yml
bump wkhtmltopdf-binary
Unlock gem 'wkhtmltopdf-binary'
Update ruby.yml
Update ruby.yml
Update ruby.yml
remove Lockfile
restore Gemfile
test only ubuntu-18.04
bundle env
remove deploy deps
remove mina dep
use rexml from bundle rather then std-lib to support ruby 3.0
install rexml
drop ruby 3.0, cleanup workflow
fix codeclimate sorting issue
Codeclimate reporting
stop using deprecated set-env
use simplecov formater
simplecov in after-build
fix yaml syntax
run in debug mode
Set correct env var to run coverage
cleanup, provide CC_TEST_REPORTER_ID secret
combine multiple results
more variables
pull/commit different envs
Change test command to get more coverage
* Create new class called ApplicationIntegrationTest, so we don't have
to override ActionDispatch::IntegrationTest
* Move UI tests to inherit from ApplicationSystemTestCase
* Existing REST API or EPP tests inherit from
ApplicationIntegrationTest.
* Move `require 'application_system_test_case'` at the end of
`test_helper`
I don't particularly agree with the Rails' convention of treating UI
tests as system tests and API tests as integration tests, but I see no
benefit in actively fighting against it.
In the future, ApplicationSystemTestCase should inherit from
ActionDispatch::SystemTestCase and JavaScriptApplicationSystemTestCase
could possibly be removed if the `driven_by` method works as it is
promised in Rails documentation:
http://api.rubyonrails.org/v5.2/classes/ActionDispatch/SystemTestCase.html
Consider introducing another class between
ActionDispatch::IntegrationTest and other items inheriting from it, as
the general Rails practice seems to have `ApplicationIntegrationTest`,
as we do have `ApplicationRecord` and `ApplicationController`.
