
Sign up to save your podcasts
Or
A call for testing is another internal post that you can share. Ideally about a week prior to launching a new feature.
The goal of a call for testing is to outline everything that you’re planning to ship and then to ask others to test it prior to launch.
Generally you do this by placing the feature behind a feature flag.
This can be a great way to catch last minute bugs and edge case issues prior to launch. It can be a great time to refine smaller things like microcopy or transitions between flows.
It can also be a great way to surface the project one more time to the folks working in support within your company. As after lunch, they’ll need to support this new feature.
Sometimes even major issues are surfaced, which is great.
A call for testing is another internal post that you can share. Ideally about a week prior to launching a new feature.
The goal of a call for testing is to outline everything that you’re planning to ship and then to ask others to test it prior to launch.
Generally you do this by placing the feature behind a feature flag.
This can be a great way to catch last minute bugs and edge case issues prior to launch. It can be a great time to refine smaller things like microcopy or transitions between flows.
It can also be a great way to surface the project one more time to the folks working in support within your company. As after lunch, they’ll need to support this new feature.
Sometimes even major issues are surfaced, which is great.