Feature BRE_FR_062 visualisation
Feature-ID: BRE_FR_062
Category: precedence
Feature-Name: precedence order
Feature-Explanation: Collation-related bracket symbols ([==] [::] [..])
Escaped characters (\<special character>)
Bracket expression ([])
Subexpressions/back-references (\(\) \n)
Single-character-BRE duplication (* \{m,n\})
Concatenation
Anchoring (^ $)
Source: Extracted from: IEEE Std 1003.1™-2017 (Revision of IEEE Std 1003.1-2008), 9.1 - matched \
ID | Search text | Regex pattern | Expected Output* |
---|---|---|---|
no test cases |
info:"Here are steps you can use to validate the precedence order of basic regular expressions using this order:
Familiarize yourself with the precedence order of the basic regular expression operators as follows, from highest to lowest:
Collation-related bracket symbols [==], [::], [..] Escaped characters Bracket expression [] Subexpressions/back-references (), \n Single-character-BRE duplication *, {m,n} Concatenation Anchoring ^, $ Write down the basic regular expressions that you want to validate.
Add parentheses to the expressions to explicitly specify the order of operations. This step is not necessary if the expressions are already fully parenthesized.
Apply the rules of precedence to each expression, working from the innermost parentheses outward. When evaluating an expression inside parentheses, follow the order of operations: first, evaluate any collation-related bracket symbols, then escaped characters, then bracket expressions, then subexpressions/back-references, then single-character-BRE duplication, then concatenation, and finally anchoring.
Compare the resulting expressions to check if the precedence order is correct. If the order is correct, the expressions should be equivalent. If the order is incorrect, the expressions will not be equivalent."
Documentation - Features for visualisation
Acceptance Criteria:
-
All acceptance criteria are fulfilled -
Diagramm displays the Regex right -
The right number of Matches and the right matches are shown
Definition of Done:
-
All Code ist commented (Docblocks, English) -
The unit tests were written, executed and passed (includes old code that is used) -
Every acceptance cirteria have at least a test case associated -
Has been peer-reviewed -
Documentation is updated -
The user interface is according to the design -
Acceptance of stakeholder