Kas legacy ff chemistry #6
Draft
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
Adds a new Gherkin feature file that defines the legacy PublicRelease field behavior, including valid bit values, default handling, and rejection of invalid inputs, along with business-level scenarios for public visibility in reports and web maps.
Error: Given a site exists where PubliRelease is false Correction: PublicRelease (missing the 'c').
Refactors PublicRelease Gherkin tests into one consolidated feature using Scenario Outlines as a configuration matrix to cover all legacy tables. Captures shared BIT semantics alongside table-specific nullability, default, and public visibility behavior in a single, maintainable specification.
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.
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
Notes
Any special considerations, workarounds, or follow-up work to note?