Once you have a sufficiently well-defined GLASS pattern,
you can use the built-in Test Data feature in GLASS Studio
to validate your custom data type.
Important: You are strongly recommended to use real-world data
samples to validate the quality of your custom GLASS
data type.
Alternatively, use synthetic data that accurately reflects the characteristics
and structure of real-world data.
Tip: Testing your GLASS data type with a
sample set of expected matches can help to identify potential issues with the
pattern before it is deployed to scan your organization's staging and/or
production environment using
Enterprise Recon.
When the Test button is clicked, the GLASS pattern
that is defined in the GLASS Studio
Visual Builder or Code Editor will be
executed on the sample data in the Enter test data pane.
Important:
The GLASS engine will display up to 500 highlighted
elements (<matched data>,
<expected matches>,
<expected matches not found>,
<false positives>) per view.
Use the controls
to scroll through and review
the highlighted test data elements.
Testing Without Manually Identifying Matches
If the Test button is clicked without
manually identifying any expected matches, matches that are found in the input
test data set will be highlighted with a blue border
(e.g., <matched data>).
Testing After Manually Identifying Matches
If the Test button is clicked after using
the Manually identify matches feature, matches that are found or not found
in the input test data set will returned as follows:
Expected Matches - Matches that were manually highlighted / identified
and found in the input data set will be highlighted with a green border
(e.g., <expected matches>).
Expected Matches Not Found - Matches that were manually highlighted /
identified but not found in the input data set will be highlighted with a maroon
border
(e.g., <expected matches not found>).
False Positives - Matches that were not manually highlighted / identified
but found as matches in the input data set will be highlighted with a purple
border
(e.g., <false positives>).
You can find a summary of the total number of
Expected Matches,
Expected Matches Not
Found and False Positives
in the TEST DATA pane and status bar.
Manually Identify Matches
To manually identify expected matches in the test data for the
GLASS data type:
In the Enter test data pane, click on Manually identify matches
.
(Optional) In the Valid Matches list on the right, select the checkboxes
for valid expected matches. This is only required if the
Test button was clicked before manually
identifying any expected matches.
Left click and drag to highlight the expected matches in the test data set.
Each highlighted match will be added to the Valid Matches list on the right.
The number of expected valid matches will be updated next to the Confirm
button.
(Optional) Click on next to a
match in the Valid Matches list to remove a highlighted match.
Once all the expected matches have been highlighted, click Confirm.
Click on the arrow at the top right
to return to the Visual Builder view.
Important:
The GLASS engine will display up to 500 highlighted
elements (<matched data>,
<expected matches>,
<expected matches not found>,
<false positives>) per view.
Use the pagination controls
to scroll through and review
the highlighted test data elements.