12 Common bugs of web application
We all know that development is quite creative and innovative work; there is always opportunity for improvement and performance optimization in web/Desktop application. Developers used to follow sometimes strict deadlines for completing their tasks, so I observed common bugs while working on different applications, which can be avoided easily by executing units tests on the behalf of development team
1.When screen is opened focus should be set on required field.
2.After displaying error message or information message, focus should be set on specific field.
3.Focus should be set on controls like Date control and Dropdown
4.Shortcut keys should be verified it should be working.
5.Field length should be fixed according to DB columns.
6.Validation should be applied on fields like Date, Password, Email etc.
7.Mandatory fields should be validated and make sure that mandatory fields are according to DB columns.
8.Error summary should be displayed properly; sometimes error summary triggers more than once in page life cycle.
9.Execute all page links; make sure that each link works fine, sometime we found that page path is not valid behind link so displays “alarming Crashing messages”.
10.Make sure that there should be no dead links on the pages.
11.If the screen is resizable, the page design (CSS+html) should be there to handle this feature. Sometimes if we resize the window, all page contents overlap each other and showing quite nasty look
12.If the window is resizable, horizontal and vertical scroll bar should be properly used.
By adding these points in your unit test check list, Development lead can reduce the bug count effectively.
1.When screen is opened focus should be set on required field.
2.After displaying error message or information message, focus should be set on specific field.
3.Focus should be set on controls like Date control and Dropdown
4.Shortcut keys should be verified it should be working.
5.Field length should be fixed according to DB columns.
6.Validation should be applied on fields like Date, Password, Email etc.
7.Mandatory fields should be validated and make sure that mandatory fields are according to DB columns.
8.Error summary should be displayed properly; sometimes error summary triggers more than once in page life cycle.
9.Execute all page links; make sure that each link works fine, sometime we found that page path is not valid behind link so displays “alarming Crashing messages”.
10.Make sure that there should be no dead links on the pages.
11.If the screen is resizable, the page design (CSS+html) should be there to handle this feature. Sometimes if we resize the window, all page contents overlap each other and showing quite nasty look
12.If the window is resizable, horizontal and vertical scroll bar should be properly used.
By adding these points in your unit test check list, Development lead can reduce the bug count effectively.
8.Error summary should be displayed properly; sometimes error summary triggers more than once in page life cycle.
ReplyDeleteCan you please elaborate it more?
Thanks for the comment :)
ReplyDeleteThis point is little bit technology related, basically in ASP.NET.we have Error Summary Control, which displays client side validation errors, we define some validation group as well, so in some cases, this summary appears twice, or same error is appeared twice in error summary. so just shared my experience, i hope you got some idea now :)
Alrite..
ReplyDeletehope i could reproduce this kind an error too someday (Devil Smile)
Thanks a lot. Was finding this answer everywhere on net and atlast found here.
ReplyDeleteThanks a lot. Was finding common bugs for desktop application
ReplyDeleteIf you share for desktop application also that would be great
"By adding these points in your unit test check list, Development lead can reduce the bug count effectively."
ReplyDeleteHow would you test those with a unit test?