Update Assertion priorities to use MUST/SHOULD instead of REQUIRED/OPTIONAL #770
Conversation
This file contains 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
howard-e
force-pushed
the
improve-results-summary-table
branch
from
f469bc8 to
f9a334f
Compare
howard-e
force-pushed
the
update-assertion-priorities-language
branch
2 times, most recently
from
e43aa51 to
ef4e6d9
Compare
howard-e
force-pushed
the
improve-results-summary-table
branch
from
4a12d0f to
703ea3c
Compare
…following migrations
howard-e
force-pushed
the
update-assertion-priorities-language
branch
from
ef4e6d9 to
a97aeb2
Compare
alflennik
approved these changes
Oct 5, 2023
alflennik
added a commit
that referenced
this pull request
Oct 5, 2023
* initial model, migration, and seeder * seeders test plan ids * test plan service * fixing migration * updating migrations to have foreign keys * Implementing Howard's feedback * Start to migrations and functions to support the DB change for further support of 648 * Add phase to TestPlanVersion * Update query and resolvers for test plan version mutations * Restored viewing of CandidateTestPlanRun * Fix graphql.schema * Rename TestPlanVersion date fields with 'status' in name to 'phase' * Add approvedAt column to TestPlanReport * Rename candidateStatusReachedAt to approvedAt * Update migration to be more clear and help in functional priority of following migrations * Start to new Test Plan Results Table * Update styling * Fix issue with submitting test results with new query shape; update blockquote styling * Add space between Run History and above TestPlanResults table on report results page * Fix optional priority string not being shown in TestPlanResultsTable component * Add missing border-bottom to test result heading on reports results page * Changes after rebase * Update Assertion priorities to use MUST/SHOULD instead of REQUIRED/OPTIONAL (#770) * Start to migrations and functions to support the DB change for further support of 648 * Add phase to TestPlanVersion * Update query and resolvers for test plan version mutations * Restored viewing of CandidateTestPlanRun * Rename TestPlanVersion date fields with 'status' in name to 'phase' * Rename candidateStatusReachedAt to approvedAt * Update migration to be more clear and help in functional priority of following migrations * Update REQUIRED and OPTIONAL assertion priorities to be MUST and SHOULD respectively * Add box back to reports --------- Co-authored-by: Erika Miguel <[email protected]> Co-authored-by: alflennik <[email protected]>
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.
Resolves #737.
This branches off of #765.