yt_answer_testing /

Filename Size Date modified Message
756 B
412 B
2.2 KB
2.1 KB
552 B
368 B
yt Answer Testing
=================

This is where answer testing for yt is set up.  The idea is that you should be
able to go into this directory and run:

    enzo_test store SOMENAME *.py

and it will run all the tests inside the *.py files.  SOMENAME should probably
be the current changeset hash.  All the parameter files located in OutputLog
will be passed into the load() function, the tests will be run, answers stored,
and then

    enzo_test compare OTHERNAME SOMENAME *.py

will compare the two results.

Currently it is not parallel-safe.

The idea is that once we have some set of tests, we can execute this on every
couple changesets, see the results, and then determine whether or not we have
ultimately succeeded in creating a stable code.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.