PSA if you hardcode test values in state to save time you WILL commit them

1. 1Identify situations where you're tempted to hardcode test values
2. 2Use a testing extension or tool to populate forms instead
3. 3Configure your development environment to separate test data from code
4. 4Test your application with mock data to ensure it works as expected
5. 5Review your code regularly to catch any hardcoded test values
6. 6Apply coding standards that prohibit hardcoding sensitive or test data

Developers and testers on a team can benefit from understanding the risks of hardcoding test values, while reviewers can help catch such mistakes before they reach production

💡 Hardcoding test values can lead to embarrassing and potentially security-risking commits, so keep test data separate from code

🚨 Don't hardcode test values in state! Use testing extensions instead 💡