WOLFRAM LANGUAGE TUTORIAL
Using the Testing Framework
Whether you are writing a single function or an entire application, Mathematica provides a framework in which to write and run tests of your code.
In the Mathematica menus, click on . It will bring up a testing notebook. (The notebook depicted here has also been saved using with name MyTests.)
Click the button to insert a test into the notebook.
In the "Input" cell, type or paste the input for your test. In the "Expected Output" cell, type or paste what the output should be.
If messages are expected to be generated upon running the tests, add them using the button. You can also add options to the individual tests such as MemoryConstraint, SameTest, TestID, and TimeConstraint using the drop-down to the right of the button.
Running Tests with the Notebook Interface
This section demonstrates running all tests in a given notebook.
Clicking the button will evaluate all tests in the testing notebook. The test results are inserted into the individual tests as they are evaluated, and upon completion of the test run, a summary of the test report is inserted at the top of the notebook. The following notebook displays the four possible test outcomes: Success, Failure, Message Failure, and Error. The button may be used to clear test results from the notebook.
The test report summary details the total number of tests run, as well as the number of successes, errors, failures due to wrong results, and failures due to messages. Additionally, a summary bar depicts the test results and has two modes for ordering the test results: by status and by sequence. When the total number of tests in a testing notebook is 50 or less, every individual tab in the summary bar links to its appropriate test. In the lower-right corner, there are two buttons that find the previous and next failed test relative to the cursor position.
Working with Test Results
Following is a success. If you wished to modify this particular test and see the outcome, you would then use the button.
Following is a failure due to a wrong result. This happens when the Actual Output is different from the Expected Output. If the Actual Output is the correct result, the Expected Output can be changed to it by clicking on the button. Subsequently, the test can be rerun by using the button.
Following is a Message Failure. Here there is an Actual Message. The test fails since there is no Expected Messages cell with that message. The button may be used to insert an Expected Messages cell with content as in the Actual Messages cell. The test may then be rerun using the button.
Following is a test Error. Fix the right-hand side of the option in the Test Options cell and use the button.
Generating .wlt Files
Click to save the tests in the notebook to a .wlt file. A file save chooser will be generated, allowing you to choose the file name and save it to a directory.
Here the file name was chosen to be MyTests2 and it was saved to the directory C:\\Users\\xyz\\Desktop. This makes a report for that file.
Here are the properties of the report.
Here are the test result rules.
This shows the expected output and actual output for the first failed test. For this test file there is just one failed test.
Click to assign TestIDs to all tests in the notebook.
Here is a test cell group with a TestID assigned.
You might want to convert a notebook of inputs, messages, and outputs into a test notebook. With that notebook being the input notebook, click on . A docked cell will then be added to the top of that notebook. Then click on the button .
Directly Running Tests in a Notebook
Single tests may be directly run using VerificationTest.
Multiple tests may be directly run using TestReport.