Application Crashing is a Severity Level one error and there is no way of accepting any kind of explanation to it. Here are some suggestions to counter that:
QA/tester Assumptions:
1. Application should be stable at all times no matter what path or action(s) performed by the user.
2. Application should treat the user in a way that the user learns from the actions about the right processes.
3. Application should log out the user or create an exception that would lead to an error page.
Testing perspective:
1. Create Test Cases based on activity logs captured if it is a .NET project. If it is a Java/J2EE based we can do handle that in session tracking.
2. Try getting on to the application from an unknown user and see if security features are met.
3. Check the work flow of the application and identify alternate paths if identified new, handled by the development team.
No comments:
Post a Comment