You are part of agile innovation team. Your team has been staying close to Hospital IT team and adapt quickly to changing conditions for the new website. The team almost always result in higher team productivity and morale, faster time to market, better quality, and lower risk than traditional approaches can achieve. Your team members are familiar with testing the happy paths, how users (Patients ) should use the software.
You team launched a web application for the Hospital after months of development. The website is going to be part of Hospital Website to provide fast and reliable services to patients. Patients will be opening an account ( Login name and password ) and then will be able to schedule meeting with the doctors, see their blood test results and make payment.
As an Agile developer, you used test-driven development from the start and achieved almost perfect test coverage. However, after months of initial product launch, you are getting mountain of bug reports in your inbox. Angry users are complaining that the software isn’t working properly and the server logs are filled with crashes. Something has gone horribly wrong despite your diligent testing.
User Complain: The user begins uploading a document from the website that your team developed. And, when the user leaves page before upload is completed (closes the browser early), the website is crashing.
User Complain: When the user accidentally enters incorrect password, the software does not take the user further and get stuck. No repose at all
What happened? And how can you fix it?
What likely went wrong and how you can modify your testing approach to ensure that your software is intuitive and error free.
Ans. As the website got stuck, the reason behind it might be heavy traffic on the website network. So many people trying to acces your webpage can lead to website crash.
This happens because:
To fix this :
Modifying testing approach :
Get Answers For Free
Most questions answered within 1 hours.