Software Testing @ glance

Steps to perform software testing: 

• Understand requirements and business logic
• Determine required standards and processes
• Set priorities, and determine scope and limitations of tests
• Determine test approaches and methods
• Determine test environment, test ware, test input data requirements
• Set milestones and prepare test plan document
• Write test cases
• Have needed reviews/inspections/approvals of test cases
• Set up test environment
• Execute test cases
• Evaluate and report results
• Bug Tracking and fixing
• Retesting or regression testing if needed
• Update test plans, test cases, test results, tractability matrix etc.

 

Components of a Bug Report: 

• Application name
• The function, module, name
• Bug ID
• Bug reporting date
• Status
• Test case ID
• Bug description
• Steps needed to reproduce the bug
• Names and/or descriptions of file/data/messages/etc. used in test
• Snapshot that would be helpful in finding the cause of the problem
• Severity estimate
• Was the bug reproducible?
• Name of tester
• Description of problem cause (filled by developers)
• Description of fix (filled by developers)
• Code section/file/module/class/method that was fixed (filled by developers)
• Date of fix (filled by developers)
• Date of retest or regression testing
• Any remarks or comments

Web based applications testing guidelines:

Apart from functionality consider the following:

• What are the expected loads on the server and what kind of performance is expected on the client side?
• Who is the target audience?
• Will down time for server and content maintenance / upgrades be allowed?
• What kinds of security will be required and what is it expected to do?
• How reliable are the site's Internet / intranet connections required to be?
• How do the internet / intranet affect backup system or redundant connection requirements and testing?
• What variations will be allowed for targeted browsers?
• Will there be any standards or requirements for page appearance and / or graphics throughout a site or parts of a site?
• How will internal and external links be validated and updated?
• How are browser caching and variations in browser option settings?
• How are flash, applets, java scripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested?

From the usability point of view consider the following:

• Pages should be 3-5 screens longer.
• The page layouts and design elements should be consistent throughout the application / web site.
• Pages should be as browser-independent or generate based on the browser-type.
• There should be no dead-end pages. A link to a contact person or organization should be included on each page.