Test suite

This wiki page gives an overview of creating a test suite for MDB Doc.

At this early stage it doesn't include all items but should give you a good starting point to exercise most of the functionality:

1. Obtain the Microsoft Northwind.mdb sample database for your version of Access. This will be supplied on the installation media or available from Codeplex.
   This is to give you a non trivial example to work from - if you have an alternative database then that could be used instead. However, you will need to ensure that various categories of data are covered.

2. Add a module with only declarations in it, for example:

    Option Compare Database
    Option Explicit

    Const ONE as Integer = 1

In the resultant file, this should be displayed within the list of modules, but not have a link to the details.

1. Add a module with the 'MDBDOC: comment feature in it:

For example:

    Option Compare Database
    Option Explicit

    Public Function AreaOfCircle(dblRadius As Double) As Double
    'MDBDOC: Calculates area of Circle. PI*radius*radius
    ' Value shown is good enough for our needs.

    Const PI As Double = 3.14159265358979

    AreaOfCircle = PI * dblRadius * dblRadius
    End Function

1. If there is no data access page in it, create one.
2. If there is no command bar, create one.
3. Run MDB Doc against the resultant file.

Now, create a new database. Do not create any objects within the database, but just run MDB Doc against it. This will create a second file, exercising the "No objects of this type found" messages.

Validating the resultant code

Once you have your two HTML files, validate the output:
7.1 Use the http://validator.w3.org to check the HTML syntax is correct (NB this can also be invoked through services such as the HTML validator addin for Mozilla Firefox).
7.2 Use http://wave.webaim.org to check accessibility and a second opinion of the first item.
7.3 Check the source code supplied resultant CSS files using the W3C CSS validator
http://jigsaw.w3.org/css-validator/
7.4 Run homepage through Lighthouse checks in Chrome/Chromium developer tools and see if any additional errors or warnings are identified.
7.5 Use the XML Tools plugin in Notepad++to validate XML content from 2.x version is well formed

Validating the documentation

8.1 Once the code is done, update the documentation to reflect changes new/amended functionality.
8.2 Use File > Check for Issues > Accessibility checker to identify issues in the source Word document. Rectify to best ability.
8.3 Use latest version of PAC tool to test generated PDFs to check Readme PDF documents are as compliant as possible. Be sure to use File > Save as PDF (not print to PDF) to generate document. Currently tested using PAC 2021.
Note that at this stage, it does not look like Word 2013 is capable of producing fully PDF/UA compliant files.