Note: The term basic search parameters refers to the list of parameters that are defined here (See parameters for all resources).
1) Creation of a 'generators' subdirectory and a parent generator class. Now that there are different types of tests being generated (SHALL/SHOULD/MAY are Interaction Conformance Tests vs. _id/_content/_lastUpdated are Basic Search Params Tests), the approach will be to instantiate a new generator for each type of test. All generators have the same generator parent class, which deals with the actual building of the scripts and the script outputting.
2) Rename 'workflow_builder' to 'blueprint_builder' (but only within that generators subdirectory. Yes, there are file duplicates within that folder and root. That's intentional as a separate PR will deal with making a generator for Interaction Conformance and removing classes that would then be relevant only in the generator subdirectory.
3) Creation of a Search Params Generator capable of creating TestScripts testing Basic Search Params on all resources supported by the given IG. This test formation relies on the SearchParameter resources, which are incomplete (_has/_type do not have any means of predicting a value for the param).
4) Addition of an 'interactions' class. I'm building this out incrementally, but the goal is to use it to replace the interactions_meta variable within the blueprint builder. However, this is the foundation of most of the logic that goes on with generation, so I'm (very slowly) double checking that it makes sense while still continuing to build it out.
To test, run the generator bundle exec bin/testscript_generator. View the (still very basic) testscripts in the generated_testscripts folder.
ms-k1ngk0ng
commented
2 years ago
This PR includes the following:
Note: The term basic search parameters refers to the list of parameters that are defined here (See parameters for all resources).
1) Creation of a 'generators' subdirectory and a parent generator class. Now that there are different types of tests being generated (SHALL/SHOULD/MAY are Interaction Conformance Tests vs. _id/_content/_lastUpdated are Basic Search Params Tests), the approach will be to instantiate a new generator for each type of test. All generators have the same
generatorparent class, which deals with the actual building of the scripts and the script outputting. 2) Rename 'workflow_builder' to 'blueprint_builder' (but only within thatgeneratorssubdirectory. Yes, there are file duplicates within that folder and root. That's intentional as a separate PR will deal with making a generator for Interaction Conformance and removing classes that would then be relevant only in thegeneratorsubdirectory. 3) Creation of a Search Params Generator capable of creating TestScripts testing Basic Search Params on all resources supported by the given IG. This test formation relies on the SearchParameter resources, which are incomplete (_has/_type do not have any means of predicting a value for the param). 4) Addition of an 'interactions' class. I'm building this out incrementally, but the goal is to use it to replace theinteractions_metavariable within the blueprint builder. However, this is the foundation of most of the logic that goes on with generation, so I'm (very slowly) double checking that it makes sense while still continuing to build it out.To test, run the generator
bundle exec bin/testscript_generator. View the (still very basic) testscripts in thegenerated_testscriptsfolder.