[Feature] Moving selected_tests inside the TestRunExecution - #1
Open
antonio-amjr wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moving selected_tests API parameter to inside the Test Run Execution model, schema and CRUD files.
That way we simplify removing one parameter from the creation API.
The following changes were provided:
selected_test, added into theTestRunExecutionmodel, is filled with the information needed (gathered from tables inside the DB). This new column is mandatory as we'll always use this dictionary to create new Test Runs.create_test_run_execution()API method had itsselected_testparameter moved inside thetest_run_execution_inobject, as a dictionary blob.