Things just before Check by Giving Your Application for QA Testing

        

This post will present you with some normal tips that you must weigh in your application before you give it for QA testing.these tips are extremely straightforward, short and general for any dialect (application).

Client Interface Side

(1) Make beyond any doubt that max cutoff is situated for all the structure fields and not more than the permitted size in the database table.

(2) Proper placeholder or directions for the structure fields are connected where needed. like,

• Enter your First Name
• most extreme document transfer size is 2mb
• acknowledged document arrangements are .png , .jpeg , .gif
• enter the mixture of scorches and numbers

(3) Proper content wrapping is sought showing any field esteem on the page (in the event of long values ).

(4) If you are permitting picture transfer, then verify that

• Legitimate greatest document size is situated.
• Permitted record sorts are characterized.
• Pictures are, no doubt erased on record erasure.
• Default picture has been set if no picture found (to show )
• Legitimate alt and title label qualities are given.

(5) Check all the spells are right. Basically check for those messages that are highlighted, connections or route.

(6) Proper messages are situated for different activities like,

• achievement message
• mistake message
• cautioning message
• data message

(7) Your configuration is cross program compatible.it would be better in the event that its responsive.

(8) An overall framed Error page, 404 page, No result discovered page is intended to be shown when any slip happens.

(9) If you have actualized any ajax call then verify that fitting transforming picture or content like handling... then again stacking... is situated that will be show until the ajax results stack in the individual territory.

(10) Proper redirections are situated all through the site.there should not be any wrong redirect.

(11) Proper acceptances connected on both the customer and server side.

Wellbeing Steps

(1) Partition of use into open and limited areas.deployment of compelling verification and approval standards.
 
(2) Form or parameters controls avoidance.

(3) Make beyond any doubt that your application is secured against all sort of Vulnerabilities like,

• Data assault
• Assaults done by including malevolent strings in inquiry strings , treats, structure fields,or in HTTP headers.
• Order execution,
• Cross-site scripting (XSS)
• SQL infusion
• Cushion flood assaults.

(4) All the sessions are protected.for the wellbeing you can scramble them.

(5) Sensitive information protection.if you are passing any parameter that has exceptionally vital part in the showcase of the page then verify that you have scrambled the activity name and parameters like id's in the url.

(6) Proper special cases taking care of.

(7) The document framework security. Client should not have the capacity to see or to get to the document structure by entering the way in the URL.

In the wake of taking after the above steps, and before giving your application to QA,

- Create a different testing environment for the analyzer to test the application instead of fundamental environment.so that any testing practice don't harm your application.