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
The idea is to have a Rakefile script that runs through the generator with differing options, putting each result into an examples folder. We would then implement a hidden dev_tests (or whatever we want to call it) generator that the script makes sure to always pass. A hidden generator is one that is not visible to the public but is nonetheless able to be invoked if you know the command.
This generator will create general sanity tests to ensure various essential functionalities of each result application is working correctly. We could ensure that our CI environment re-generates these results and runs these tests, thereby preventing a scenario where we pull something that breaks the generator apps.
Whether or not we include the examples directory in source control I guess is optional, but I'd be worried that they would sometimes be stale since they would rely on the user making sure to re-generate of their changes.
create Rakefile script to generate apps into examples folder
ensure that Coveralls, the various linters (actually, we could keep the JS linters), are set up to ignore it
create hidden dev_test_generator
have generator results script use this option when generating the apps
have Rakefile include generated app tests when running test suite
move spec/dummy tests to the dev_test_generator and delete dummy apps (optional because this wouldn't work as far as ensuring React v13 compatibility)
ensure our CI environment handles all of this appropriately
refactor so that we do not unnecessarily rebuild the app, re-run bundle install, or re-run npm install when we don't need to do so
incorporate the ability to generate the apps in a separate location and push them to a given GitHub (basically the generator results functionality)
The text was updated successfully, but these errors were encountered:
@justin808 this has been on hold while I've been working on other things, but it's actually just about ready to go after I make some performance optimizations. Should be really cool! This is what allows us to have CI ensure the generator apps actually work!
The idea is to have a Rakefile script that runs through the generator with differing options, putting each result into an
examples
folder. We would then implement a hiddendev_tests
(or whatever we want to call it) generator that the script makes sure to always pass. A hidden generator is one that is not visible to the public but is nonetheless able to be invoked if you know the command.This generator will create general sanity tests to ensure various essential functionalities of each result application is working correctly. We could ensure that our CI environment re-generates these results and runs these tests, thereby preventing a scenario where we pull something that breaks the generator apps.
Whether or not we include the
examples
directory in source control I guess is optional, but I'd be worried that they would sometimes be stale since they would rely on the user making sure to re-generate of their changes.examples
folderdev_test_generator
dev_test_generator
and delete dummy apps (optional because this wouldn't work as far as ensuring React v13 compatibility)The text was updated successfully, but these errors were encountered: