Documentation support - how to use staging to test

[Jenny-yw]

Request type

• Writing new documentation
• Updating previously published documentation
• Reviewing recently written, never-before-published drafts

Number of docs

1

Subject matter expert

Jenny Wang

Approvals

No response

Embedded media

• Screenshot(s)
• Diagram(s)
• Video(s)

Audience

• Developers
• Designers and researchers
• Product managers
• Other

Anything else?

When testing in a live environment (including staging), you want to share password at the time of study and reset it after each participant. For simplicity, the passwords are according to the participant's number, i.e Participant01, and make sure to track passwords in the sensitive repo. Also, make sure you are up on the test account maintenance schedule (I think the 2nd Tues in a month) and put notices in every conceivable channel the dates you plan to test on staging so no one messes up your sessions.

[jknipes]

Hi @Jenny-yw , thanks for your content suggestions. The Platform Content team will review your request and put it in our backlog to refine for next steps.

[jknipes]

@Jenny-yw where do you feel this guidance should live on Platform Website?

[Jenny-yw]

@jknipes It should have its own page under Conducting sessions. Could this visual guide also be added?

[naomimarcussen]

@Jenny-yw Can you point to the test account maintenance schedule you've used?

[sudeeptibh]

I'm adding some additional suggestions. I would like a dedicated section for testing in staging that goes over the logistics of testing in staging. How do you test with users in staging? How do you select which test users to use? Do you need to get prior approvals for this? Example guidance to put in your conversation guide etc.