Testing.md

@@ -3,9 +3,9 @@
 ## Phase 1 (from the end of January 2011 to the end of April 2011) **Done**
 
 1. Analyze areas of functionality to be tested, strategy for testing them, and identifying test cases to be created.
-   * See Testsuite
+   * See [[TestSuite]]
 2. Review automated test frameworks, and select one.
-   * See Automated Test Framework. Our choice is Selenium. We plan to move to Selenium 2 as soon as it is released to gain support for Opera. Google is also providing Selenium support for mobile devices, which we will use as it becomes available.
+   * See [[Automated Test Framework]]. Our choice is Selenium. We plan to move to Selenium 2 as soon as it is released to gain support for Opera. Google is also providing Selenium [support for mobile devices](http://code.google.com/p/selenium/wiki/WebDriverForMobileBrowsers), which we will use as it becomes available.
 3. Create a test plan. After preliminary discussions with Frédéric, our plan is:
    * Create Selenium ref tests for LaTeX and MathML processing, rendering, and UI testing that can be automated.
    * Create "scenario tests" for installation, configuration, API and UI testing that can't easily be tested with Selenium ref tests.  The scripts in the current ./test directory can be thought of as an initial step in this direction