You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you super scaffold a model we'll generate a tests for the api controller that we generate, but we do not generate a test for the user-facing controller. It would be nice if we did.
For instance, if you run this:
rails g super_scaffold List Team name:text_field --navbar="ti ti-list"
Then we generate a bunch of files, two of which are controllers:
If you super scaffold a model we'll generate a tests for the api controller that we generate, but we do not generate a test for the user-facing controller. It would be nice if we did.
For instance, if you run this:
Then we generate a bunch of files, two of which are controllers:
But we only generate one controller test:
The api controller test is based on
test/controllers/api/v1/scaffolding/completely_concrete/tangible_things_controller_test.rb
in the starter repo: https://github.com/bullet-train-co/bullet_train/blob/main/test/controllers/api/v1/scaffolding/completely_concrete/tangible_things_controller_test.rbThe starter repo also has an
account
level test attest/controllers/account/scaffolding/completely_concrete/tangible_things_controller_test.rb
: https://github.com/bullet-train-co/bullet_train/blob/main/test/controllers/account/scaffolding/completely_concrete/tangible_things_controller_test.rbMaybe we can use that as the template for a test for the user-facing controller?
The text was updated successfully, but these errors were encountered: