##// END OF EJS Templates
DEV: Separate FileCheckpointManager and GenericFileCheckpointManager....
DEV: Separate FileCheckpointManager and GenericFileCheckpointManager. - Adds a `GenericCheckpointMixin` as a helper for implementing the two boundary-traversing Checkpoint API methods, `create_checkpoint` and `restore_checkpoint`. - `GenericFileCheckpointManager` is implemented as a subclass of `FileCheckpointManager` using `GenericCheckpointMixin`. Note that this is the safe subtyping relationship because of method signature *contra*variance: `FileCheckpointManager` accepts `FileContentsManager` in its method signatures type, whereas `GenericFileCheckpointManager` accepts any `ContentsManager`. - Moved Checkpoint-related classes to their own files.

File last commit:

r15262:24772f02
r19838:4cce9bcf
Show More
README.md
28 lines | 932 B | text/x-minidsrc | MarkdownLexer
Brian E. Granger
Updating JS tests README.md.
r15262 # IPython Notebook JavaScript Tests
Paul Ivanov
updated js tests README, --port= now optional
r13271
Brian E. Granger
Updating JS tests README.md.
r15262 This directory includes regression tests for the web notebook. These tests
depend on [CasperJS](http://casperjs.org/), which in turn requires a recent
version of [PhantomJS](http://phantomjs.org/).
David Wyde
Add a README for CasperJS tests.
r13250
Brian E. Granger
Updating JS tests README.md.
r15262 The JavaScript tests are organized into subdirectories that match those in
`static` (`base', `notebook`, `services`, `tree`, etc.).
To run all of the JavaScript tests do:
Paul Ivanov
updated js tests README, --port= now optional
r13271
```
iptest js
```
Brian E. Granger
Updating JS tests README.md.
r15262 To run the JavaScript tests in a single subdirectory (`notebook` in this
case) do:
David Wyde
Add a README for CasperJS tests.
r13250
Brian E. Granger
Updating JS tests README.md.
r15262 ```
iptest js/notebook
David Wyde
Add a README for CasperJS tests.
r13250 ```
Brian E. Granger
Updating JS tests README.md.
r15262 The file `util.js` contains utility functions for tests, including a path to
a running notebook server on localhost (http://127.0.0.1) with the port
number specified as a command line argument to the test suite. Port 8888 is
used if `--port=` is not specified. When you run these tests using `iptest`
you do not, however, have to start a notebook server yourself; that is done
automatically.