A very basic introduction to SQA tasks for a small project group

Introduction

In the general software development process we go through several phases and follow numerous design techniques. Among the design strategies multi layer abstraction based design is mostly followed where the solution is divided into:
1)Core Backend Namespace/Classes/Functions
2)Front end Controller page file
2.1) External Javascript Files
2.1) internal Javascript codes
3)Back end database script(Stored Procedure/Views/Triggers)

So what is the matter ?

In our development process when we receive the HTML file we often convert various dummy links.Also we often use some javascript codes. During development,unit testing,debugging we print many debugging codes such as alert();, Request.current().print(),Console.print() etc.. These are the places where we need to be careful for SQA tasks. IF we forget to comment/remove those kind of messages, the secrets of programming magic will appear in front of our clients ;).
Also when integrating modules, we forget to specify correct anchors of several pages.Those need care and attentions.

Another thing to remember in some dynamic web modules,in development process,we fetch records from database with the help of resultset(s) object and use the data in many sections of our code. Often while programming we first insert the data in the table and then do wroks and test unless it's a module of insertion. The key point is that, if the code chuck is not handled properly or execption is not handled, the resultset may return null or it can contain no data. This can be a scenario for testing.
A possible solution for that can be, while testing we can truncate all the tables that contains dynamic data(Not static data table) and then re check our pages. The flaw will come out if there is any on those pages.

The checklist :

1) Remove all unused debugging print type of codes
2) Remove debugging alerts() from JS file
3) Re check the page anchors
4) Truncate the DB and then re-run and re check the modules

Conclusion

Software Quality comes with experience and experience comes with fighting with these types of barriers. Hope these sets of idea helps somebody who knows all these things but was out of mind untill reading this article.