Testing convention cuts down estimated testing time

There are different types of coding conventions, file & folder naming conventions and people are following these practices in their day to day work.

From my practical work, I like to share with you one of my experience regarding testing convention. I am talking about one of our product which has form submission section with a lots of controls. Moreover, we need to verify different categories of forms with numerous number of fields. So, there is a chance of data missing/losing and so as. In a nutshell, I/we need to verify all fields mapping. Say Form1 has 133 controls (textbox or rich textbox) and how these were verified accurately at the time of verification, for Form1 I had put values like this way -

Legend:

N = number of form(s)

X = number of field(s)

You can use auto filler or record player for this purpose. After publishing the form I had cross checked data from published section, printer version and DB as well. We had very short deadline period, forms were developed one after another. After completed my one from saved data were found by the following pattern -

By seeing at a glance I had verified form(s) so accurately. Another thing, that I had used script tag that helps me to verify the HTML converting test case. If any field suffering from decoding problem it gives alert like this way -

By seeing the above alert pop-up, I have very swiftly track the field(s) which has flaw. That will also help in the time of bug reporting precisely.

This tips and tricks will cover following test cases:

1. Data mapping on published page, printer friendly HTLM version and DB - Yes/No
2. Data losing in any field of any form - Yes/No
3. Fields existence on printer version - Yes/No
4. HTML decoding in all fields - Yes/No
5. Special character converting - Yes/No
6. Form wise report in the time of regression testing - Yes/No

Now- a-days, we are going to implement Agile development. So, in terms of Agile testing process we need to follow the testing convention which cut down the estimated testing time. This is one of my techniques. Maybe, you use another better one.