Tag Archives: Testing

Change the testers hiring process

Current process: The typical questions were “What tech do you know?” “Do you know these tools?” and not much more than that. If someone got along with the interviewer and his answers had been adequate or better, the company would extend an offer.

My observation: I looked at the good testers around me and tried to identify the “whys” of their success. All of them were driven to learn and capable of adapting to change. If they didn’t know a tool or a tech, they learned it. Because under the hood, testing is learning and relearning software everyday. The following are seven changes I made to my interviewing process.

Change One: Stop Asking Tech and Tool Questions First
It’s much more important to find the right mentality. My first interview is now mostly personality based. Followed by, how would you test this, where this’is a generic thing— like a vending machine, a trash bin, or a telephone. I leave it generic enough to encourage the person to start out with questions. The best testers ask lots of questions instead of diving into examples of how they would test, questions like “How much time do I have?”  “What resources do I have?” “What is the goal of this testing?” and on and on and on. Good testers are capable of assuming what kind of this it is and break the problem down into good examples of high-level test design and low-level test specifics.

Change Two: Never Rely on Just Yourself to Interview People
You can be biased and ignore glaring errors that others spot. You might have an off day. Maybe you and this person just mesh and you don’t finish your due diligence, consciously or unconsciously.

Change Three: Write a Job Description, Not a Person Description
Testers are a very diverse bunch; what you want someone to accomplish in a job position can be accomplished many different ways. You don’t know ahead of time what specific skills that will require, but you do know what goals you want accomplished by this person in three-to-six-to-twelve months (don’t you?). I’ve found some of my best testers from all walks of life: ex-Microsofters, HVAC repairmen, high-school drop-outs, and mechanical engineers. Figure out what the job description should be and don’t assume what skills you need to get the job accomplished.

Change Four: Put Them In a Stressful Situation
Testing is stressful; your job is to prove to people how ugly their baby is. Give them to a test a small website and find their “most important” bug.

Change Five: Retrospect, Reflect, and Improve!
Finally, keep a record of the people you interview and when. Did they get a second interview? Why? Did they make it past the second interview? Why? Did you make them an offer? Did they accept? How did they do after they’ve been there three-to-four months? Can you make changes to the way you interview to weed out the people who didn’t work out in three-to-four months? Or to isolate the people that are doing awesome after three-to-four months? Interviewing is not a static exercise; don’t treat it as such.

 

Web testing checklist

Web Testing checklist

1.  Functionality testing

 

Sno.

Items to be checked

Yes / No / NA

Remarks

1.       

Content Testing

 

 

2.      

Are text in the web page checked in terms of fact, spelling and grammar?

 

 

3.      

Are images in the web page checked for their size and color?

 

 

4.      

Are the volume, replay, and auto-start of the audio/video components in the web page checked?

 

 

5.      

Are the alignment, formatting, wrapping issues and size of text checked?

 

 

6.      

Is the alignment of controls such as radio buttons and check boxes checked?

 

 

7.      

Is there a check made for Broken Links in the web page?

 

 

8.      

Are the unnecessary links and buttons in the page removed?

 

 

 

 

 

 

 

Form testing

 

 

10.   

Are text boxes validated for nulls, special characters, spaces and maximum size?

 

 

11.   

Are the initial values of check boxes and radio buttons correct?

 

 

12.   

Is only one radio button in a group allowed to be checked at a time?

 

 

13.   

Do the check boxes and push buttons trigger the desired event?

 

 

14.   

Are all the date formats uniform in the web pages?

 

 

15.   

Are the appropriate alert messages displayed(ex: if the user does not have adobe then it has to give  alert message)

 

 

16.   

Is the Order of the links the same in all pages?

 

 

 

 

 

 

Database Testing

 

 

17.   

Does the application locate the intended database?

 

 

18.   

Is addition of duplicate record allowed?

 

 

19.   

Is addition / modification / deletion of record in the database checked?

 

 

20.   

Is password encrypted and saved in the database?

 

 

21.   

Is there any reference in any ‘FORM’ about the DATABASE ‘LOGIN NAME’ and ‘PASSWORD’?

 

 

22.   

If  ‘yes’ is the form protected?

 

 

23.   

Is there any folder shared for ‘backup’ purpose?

 

 

24.   

If  ‘yes’ is it protected?

 

 

 

 

 

 

 

Functional Issues

 

 

25.   

If the user checks a check-box, goes back one page, and then forwards one page, is the check box still checked?

 

 

26.   

If the browser is resized, does the content still display properly?

 

 

27.   

Does the page display correctly, when refreshed?

 

 

28.   

Should certain controls be disabled or grayed out under certain conditions?

 

 

29.   

Are the sessions closed after the user does not use the web page for some time (say 30 minutes) or the user closes the browser instead of  ‘logoff’?

 

 

30.   

Are cookies there in the application?

 

 

31.   

If  ‘yes’ are the cookies retrieving the data?

 

 

2. Usability Testing

 

S.No.

Items to be checked

Yes/ No/ NA

Remarks

 

Accessibility

 

 

1.      

Does the URL contain human-readable directory and file names that reflect the nature of the information space?

 

 

2.      

Does it contain a Home page, which gives easy understanding of the features and purpose of the web site?

 

 

3.      

Does the Home page give details about the contact person’s name, address, phone, fax and

E-mail?

 

 

4.      

Does the Default mail client open with  new message window and the right contact e-mail address in the To location bar on clicking mailto option?

 

 

5.      

Is the “look-&-feel” of the page same across browsers?

 

 

6.      

Does the site make effective use of hyperlinks to tie related items together?

 

 

7.      

Is page length appropriate to site content and scroll bar available to commensurate with page length?

 

 

8.      

Does the page display the same across various display settings?

 

 

9.      

Do all the images have alternate text in the page?

 

 

 

Performance

 

 

10.   

Is it moderate in use of graphics and images that limit loading time?

 

 

11.   

Is load time acceptable, even in a slow dial-in connection?

 

 

 

Form Use

 

 

12.   

Whether the format of the input is displayed to the user if data has to be input in a certain format (i.e., dates, first name followed by last name)?

 

 

13.   

Does the form include a facility for clearing or resetting the form with clearly labeled buttons?

 

 

14.   

Are Feed back messages or error messages displayed using easily readable font and color?

 

 

15.   

In reports are headers, footers, and page numbers taken care?

 

 

 

Navigation

 

 

16.   

Does the site use standard link colors?

 

 

17.   

Are the links descriptive of what the user will find upon visiting?

 

 

18.   

Does the page contain a link up to the home page?

 

 

19.   

Does the site have a map, navigational bar or a set of instructions on how to go from one page to another?

 

 

 

Readability

 

 

20.   

Does it use language that is comfortable for its users?

 

 

21.   

Is Density of the page appropriate?

 

 

22.   

Is the site moderate in its use of color, scrolling text, blinking text, and marquee style text? Does it avoid juxtaposing text and animation’s?

 

 

23.   

Is splitting page into frames not confusing?

 

 

24.   

Is relative-width tables used to fit the window browser?

 

 

25.   

Does the site have a consistent, clearly recognizable “look-&-feel” across the site?

 

 

26.   

Is ‘HELP PAGES’ provided for all the pages?

 

3. Compatibility Testing

 

SNo.

Items to be checked

Yes/

No/

NA

Remarks

1

Is the web site tested for compatibility across different operating systems like Windows 95 / NT 4.0 / 2000, Mac, Linux, Unix?

 

 

 2

Are the contents printed properly, if printed in different printers?

 

 

3

Is the web page viewed properly with all the available browsers in the market like IE, Netscape, AOL, WebTV etc. & the various versions of it?

 

 

4

Is the web page viewed properly with all the possible screen resolutions – 640 x 480, 800 x 600, 1024 x 768, 1280 x 1024?

 

 

5

Is the web page compatible with all the monitor color resolutions – 16-bit, 24-bit, 256-color etc.?

 

 

 

4. Performance testing

 

SNo.

Items to be checked

Yes/No/NA

Remarks

1

Is the response time of the application checked for both the peak hours and normal hours?

 

 

2

Has the maximum number of concurrent users supported by the application been tested?

 

 

3

Is the impact of employing security technology on the performance of the application tested?

 

 

4

Have the areas in which the application performs well or have bottlenecks been identified and tested?

 

 

 

 

 

5.Configuration Testing

SNo.

Items to be checked

Yes/No/NA

Remarks

1

Are the versions of the updated web pages recorded?

2.

Is there any change due to the updated web pages?

 

 

6. Security testing

 

SNo.

Items to be checked

Yes/No/NA

Remarks

1

Are all the open and closed ports in the machine tested?

 

 

2

Is the machine’s resistance to vulnerability tested over a period varying length?

 

 

3

Has the scope of security testing been clearly defined?

 

 

4

Is the SSL encryption mechanism checked?

 

 

5

Does penetration test check the place of controls and also the conventional security issues?

 

 

6

Does penetration testing evaluate an enterprise’s intrusion detection and response capability?

 

 

7

Does penetration testing provide an empirical method for determining machines with sufficient security?

 

 

8

Is Security for password taken care?(locking after 3 times, using encryption for password etc)

9

Are the displayed items in the screen according to the user privileges?