Pre-release test result datasets

Identifies documents containing references to pre-release test result datasets in Australian contexts. Higher confidence identifies datasets of executed tests for not-yet-released builds (result rows with pass/fail outcomes tied to a candidate, RC, or unreleased build identifier); general QA and testing vocabulary remains discovery-only.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth), GDPR
Frameworks: ISO 27001, ISO 27701
Data categories: intellectual-property
Scope: wide
Risk rating: 7
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:pre[\s-]+release\s+test\s+results|test\s+dataset|test\s+results|quality\s+assurance|regression\s+testing|validation\s+results|pre[\s-]+release\s+testing|test\s+report|acceptance\s+testing|performance\s+testing)\b

Corroborative evidence keywords

pre-release test result datasets, pre, release, test, result, datasets, product, quality, safety, My Health Record, pathology result, diagnostic imaging, discharge summary, prescription record, immunisation history, immunization history, organ donor, clinical trial, medical history, allergy (+30 more)

Proximity: 300 characters

Should match

pre-release test results — Primary topic phrase match
test dataset — Case-insensitive topic phrase match
test results — Alternative topic phrase match
quality assurance — Additional topic phrase match
TC-881 | FAIL | build RC-2027.04 | latency 842 ms | expected <500 ms TC-882 | PASS | build RC-2027.04 — Executed test-result rows tied to a release-candidate build (enforces at 75/85)

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
product failure — Generic word pair from old broad template should not match
Regression testing guide for released version 4.0. — Testing discussion without candidate-build result rows — discovery only, must not enforce
The school test results were mailed to parents. — Educational results, not product testing — must not enforce
QA training sample: TC-001 | PASS | build RC-DEMO. — Training/sample and demo markers identify synthetic data — suppressed from enforcement
test results — Heading alone supplies no dataset or lifecycle evidence — discovery only, must not enforce

Known false positives

Common words and phrases related to pre-release test result datasets appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.

References

https://www.productsafety.gov.au/product-safety-laws
https://www.safeworkaustralia.gov.au/doc/model-code-practice-how-manage-work-health-and-safety-risks