Version 21 by Kerry Lamb
on Dec 09, 2008 14:51.

<< Changes from 20 to 21
compared with
Current by Kerry Lamb
on Jun 17, 2009 16:31.

 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 2 changes. View first change.

 Descriptions and best practices for a variety of testing-related activities used throughout the software development life cycle. Please comment and contribute\!
  
 h4. [Unit testing]
  
 The lowest level of testing performed during software development, where individual units of software are tested in isolation from other parts of a program.
  The lowest level of testing performed during software development, where individual units of software are tested in isolation from other units; the smallest software component.
  
 h4. [Functional testing|Functional Testing]
  
 Testing to ensure that the edits, processes, and outputs conform to the specification or expectation. This level of testing is concerned with the entire system, not just small pieces or units of code. A common way of differentiating between unit testing and functional testing is to ask whether the order of the tests matters. If the order matters, the test is part of functional testing.
  
 h4. [Security testing|Security Testing]
  
 Testing to find vulnerabilities in the application which could allow accidental or malicious access, misuse, modification, destruction, or disclosure of the application or data.
  
 h4. [Regression testing]
  
 Testing to ensure that previously-working software continues to work as intended, and to detect unintended consequences resulting from program changes.
  
 h4. [Stress testing]
  
 Testing to verify the stability of the system while executing with a high volume of data, or under conditions of insufficient resources (such as memory or disk space), of unusually high concurrency, or of sustained high loads.
  
 h4. [Usability testing]
  
 Testing to assess ease or efficiency of use through the study of user interaction with a product or product simulation.
  
 h4. [Accessibility testing|https://www.washington.edu/computing/accessible/accessibleweb]
  
 Testing to demonstrate the degree to which a system is usable by as many people as possible without modification, often focusing on people with disabilities.
  
 Here is a link to the Accessibility Evaluation Procedure (Draft): http://www.washington.edu/accessibility/accessibleweb/eval_proc.html
  Here is a link to the Accessibility Evaluation Procedure (Draft): [http://www.washington.edu/accessibility/accessibleweb/eval_proc.html]
  
 Contact Rick Ells for more info.&nbsp;
  
 Also, JAWS is a screen reader that can be used for testing.&nbsp; See&nbsp;[http://www.freedomscientific.com/fs_products/JAWS_HQ.asp] for more information.
  
 h4. [Interoperability testing]
  
 Testing to verify if computer systems or software applications/components can operate and interact smoothly.
  
 h4. [User Acceptance testing]
  
 Testing to enable the 'owners' (clients) of the product to finally accept the product deliverables or application.
  
 h4. [Code review]
  
 A testing technique where source code logic and structure are traced manually in a meeting of interested technical parties to analyze the programmer's logic and assumptions.
  
 h4. [Test Results/Defect tracking|Test Results and Defect tracking]
  
 Testing activities to identify test coverage (which tests have been run, passed, and failed), and document the status of issues which have been discovered during testing and other development processes.
  
 h4. [External Interface (Data Exchange) Testing]
  
 Testing to verify the connection between two or more entities.
  
 h4. [Test Management]
  
 A summary of the management/administrative activities that relate to testing.&nbsp;