Software Testing

Posted on 2005-04-21
Last Modified: 2010-04-17
I've finished writing an application and now it needs testing.

I'd like somebody else to do it but i'd like to be able to write a "Testing Strategy Document" of some sort so somebody can follow it, with me safe in the knowledge it's being tested properly.

How might one of these documents look?

Any advice greatly received.

Question by:Type25
    LVL 23

    Expert Comment

    what type of application is it ? Does it require data entry or is it a multi media application ? I mean obviously the type of application it is will affect what type of testing you do on it to a certain extent ie if it is for data entry then you will test valid input ranges ie if you have to enter ages you dont want someone to be able to input -21 or 204 so you would need to test for range ( only able to input between 0 and 100 ) or something to that extent, where as if it is a multimedia application then you would test for other things like does the application crash out with any format(s) or media it is supposed to play ?

    Does it have incompatability issues with any hardware, if so then it will need work arounds or alterations.

    Just to give you an idea :)

    So if you could ellaborate on what the application is or what it does, etc. Then I am sure we could help you further :)

    Correct me if I am wrong ?? :D
    LVL 8

    Expert Comment

    LVL 3

    Accepted Solution

    I coauthored a book on testing (free PDF here: and was a tester for many years.  There are all kinds of document formats and junk floating around, but I found the easiest document style to accomplish what you are asking was a table created in OpenOffice (or WordPerfect or Word) that looked something like this:

    Tester Name:
    Test Date:
    Test             |  Expected Result           |   Defect Number if failed                           |  Passed     |  Failed

    Then, you would write something like, "Enter 300 characters in the input field" in the Test section.  Expected Result would contain something like, "You shouldn't be able to add more than 20 characters to the input field".  Then, if the tester entered 300 characters and blew up the program, he would write up a defect and enter the defect number in the Defect Number if Faild field and then check Pass or Fail depending on the result of each test case.

    I have seen a lot of fancy stuff, but this type of document was easy to read and walked somebody through the entire program (or should anyway).  Not only is it a great test case document structure, but it also helps train new employees on the program quickly because they have a step by step guide to look at.
    LVL 9

    Author Comment

    Right OK, basically the application is a web-based business app written in ASP.NET, it's to run only on Internet Explorer, but it will be run over the internet by various selected companies (which will abide by our rules).

    I like your ideas and why i understand this level of testing, what i'm really after is writing a high level document on the 'areas' that need testing.

    In other words i don't want to go through all 50 aspx pages and write down all the column lengths and make sure they don't exceed what's expected.

    I was thinking something more like.

    1) What the application is run like on different resolutions
    2) What settings need to be in place on IE (popup blocker etc)
    3) What versions of IE will it differ on
    4) Testing column lengths  (by this, enter random values and make sure it doesn't break!)
    5) Other.. (?)

    ChastityMan, i guess i could use your method to further break down the options above.

    LVL 23

    Expert Comment

    What about testing it across different platforms ie different web browsers such as Opera, firefox, etc ? ( Just a thought ). BTW the testing that I Had to do with regards to my course work within my I.T A Level was the same as what chastity man suggested and I have a ream of pages that are like that with regards to different area's of the application I made for my coursework.

    Good job he ellaborated on that !

    Kind Regards


    Featured Post

    Do You Know the 4 Main Threat Actor Types?

    Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

    Join & Write a Comment

    Suggested Solutions

    This article is filled with multiple code samples and explanations for mathematical calculations. They are as follows: 1. General tips 2. Quadratic formula 3. Object collision 4. Projectile path General Tips       Here are some of my tips f…
    A short article about problems I had with the new location API and permissions in Marshmallow
    An introduction to basic programming syntax in Java by creating a simple program. Viewers can follow the tutorial as they create their first class in Java. Definitions and explanations about each element are given to help prepare viewers for future …
    In this fifth video of the Xpdf series, we discuss and demonstrate the PDFdetach utility, which is able to list and, more importantly, extract attachments that are embedded in PDF files. It does this via a command line interface, making it suitable …

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now