##master-page:HomepageTemplate
#format wiki
<<Include(Testing/Header)>>

==== Works ====
 * AutomatedTestsForAnjuta
 * AnatomyOfATestCase

==== Quality Assurance ====
 * Functionalities tests
 * Unit testing on the API
 * Documentation strings testing :
  * Are all documentation strings present ?
  * Are they useful ?
  * Are there broken links?
  * Tooltips
 * GUI testing :
  * Does the program conforms to [[httpp://library.gnome.org/devel/hig-book/stable/ | Gnome Human Interface Guidelines ]]
  * [[http://live.gnome.org/UsabilityProject | Visual Design]]
 * [[ http://en.wikipedia.org/wiki/Code_review | Code Review]]

==== Why GNU/LDTP ? ====
 * Very powerfull design. <todo: explain why this design is so powerful>

 * Powerfull technological choices :
  * User interface is describe by a language. <todo: explain why this gives power>
  * Test reports are XML documents.
   This gives us the ability to :
   * Automatically send the test report to a central server which will process the test report after authenticating the user.
   * Many other things <todo: list here those other things>

==== Some Links about the science of software testing ====

 * [[https://code.edge.launchpad.net/ubuntu-desktop-testing]] 
 * https://wiki.ubuntu.com/Testing/Automation/Desktop/
 * http://live.gnome.org/TestingUsingAtSpi
 * http://live.gnome.org/DesktopTesting
 * https://launchpad.net/gnome-desktop-testing
 * http://launchpad.net/gnome-desktop-testing/trunk/0.1/+download/gnome-desktop-testing.tar.gz
 * http://en.wikipedia.org/wiki/Software_testing
 * http://en.wikipedia.org/wiki/Code_review
 * [[http://safsdev.sf.net/ | Software Automation Framework Support]]
 * http://safsdev.sourceforge.net/DataDrivenTestAutomationFrameworks.htm#TheApplicationMap
 * [[https://litmus.mozilla.org | Mozilla Litmus]]
 * AutomatedProblemReports
 * [[https://launchpad.net/pqm | Patch Queue Manager (PQM)]]
...

----
CategoryHomepage