Intermittent form config test failure -- missing introduction function

[cvalarida]

User Story

As a front end engineer, I need to be able to rely on the build not failing randomly so I can merge my changes in a timely manner without rerunning the build.

Background

I ran across a broken test on one of my branches. It said the form 22-5495 had a missing introduction function. Rerunning the build without changing anything worked fine.

This has happened to others as well.

Other examples

Branch	Failing test	Failing build	Successful build
update-json-schema-version	22-1995	Build 1	Build 2
cta-helpers-alphabetize	22-0994	Build 2	Build 3

Acceptance Criteria

• [ ] The builds don't break intermittently because the test cant find the form introduction

Possible reasons

:man_shrugging: Only thing I can think of is something is more asynchronous than it lets on. I'm not sure what that would be yet.

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, triage, tools-improvements)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, call center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[erikphansen]

doubt it's helpful at this point, but I found another two: http://jenkins.vfs.va.gov/blue/organizations/jenkins/testing%2Fvets-website/detail/vagov-1330-trigger-information-must-be-a-button-keyboard-focusable/1/tests/ and http://jenkins.vfs.va.gov/blue/organizations/jenkins/testing%2Fvets-website/detail/vagov-1330-trigger-information-must-be-a-button-keyboard-focusable/3/tests

[timwright12]

Kicking over to design system