Menu
I'm working with good group of very sharp developers on one of my client's premises. We are coding correctly around NullPointerException and other exceptions, so we don't have those. But when it comes to business rules we have some mistakes and find issues when already in production. Granted we have very fast paced environment, and deployment to production commanded by management team, not development one. But we passed "green light" with QA and Data Quality teams.
What are the best practices to find business related bugs early in software development process.
278
#1) Understand the whole application or module in depth before starting the testing. #2) Prepare good Test Cases before starting with testing. I mean give stress on the functional test cases, which include the major risk of the application. #3) Create sufficient Test Data before tests.
a) Alpha Testing Alpha testing is a type of acceptance testing performed by the team in an organization to find as many defects as possible before releasing software to customers.
Make it easy and clear to let the developer know the exact failure of the software. You also let the developer understand and experience the bug for an expected fix. In order to achieve this, the tester should verify the issue first.
"What are the best practices to find business related bugs early in software development process."
Several things.
Use Cases.
Overall Tests based on the Use Cases.
Unit Tests based on the Use Cases.
The important thing is to tie the system -- as a whole -- to real actors, real business value. It's too easy to focus on technical issues. To avoid narrow focus on technical issues, have use cases and test against those.
88
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
