Opened 13 years ago
Closed 2 years ago
#8754 closed enhancement (invalid)
sagenb -- add "how to test" directions to the sagenb README.txt
Reported by: | William Stein | Owned by: | jason, was |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | notebook | Keywords: | |
Cc: | Frédéric Chapoton | Merged in: | |
Authors: | William Stein, Alex Leone | Reviewers: | William Stein |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
1. Doctest: sage -t -sagenb 2. Run the Selenium test suite: sage -python sagenb/testing/run_tests.py To use Selenium, you must visit http://seleniumhq.org/download/ and: * Download and extract Selenium RC ("the Selenium Remote Control") * Run it as follows on Linux: $ cd /path/to/selenium-remote-control-1.0.3/selenium-server-1.0.3 $ java -jar selenium-server.jar $ cd /path/to/sagenb-0.8/src/sagenb $ sage -python sagenb/testing/run_tests.py * Run it as follows on OS X: $ cd /path/to/selenium-remote-control-1.0.3/selenium-server-1.0.3 $ cd /path/to/sagenb-0.8/src/sagenb $ sage sage: import sagenb.testing.run_tests as rt sage: rt.setup_tests('localhost', False, '*firefox') sage: rt.run_any()
That the instructions for OS X are different is probably a bug.
Attachments (3)
Change History (14)
Changed 13 years ago by
Attachment: | trac_8754-sagenb.patch added |
---|
comment:1 Changed 13 years ago by
Status: | new → needs_review |
---|
comment:2 Changed 13 years ago by
Status: | needs_review → positive_review |
---|
Changed 13 years ago by
Attachment: | trac_8754-sagenb.2.patch added |
---|
comment:3 Changed 13 years ago by
Authors: | → William Stein, Alex Leone |
---|---|
Reviewers: | → William Stein |
Changed 13 years ago by
Attachment: | trac_8754-sagenb.replaces2.patch added |
---|
Newest Version. Added a "Reviewing Patches" section. Apply only this.
comment:4 Changed 12 years ago by
Status: | positive_review → needs_work |
---|
Should someone review the latest patch? I noticed two minor problems:
dwnload
- An extra
*
inb) * Run it as follows:
Also, should the reviewing section first refer in some way to steps 1,2,3, and/or 6 of the development section?
comment:5 Changed 9 years ago by
Milestone: | sage-5.11 → sage-5.12 |
---|
comment:6 Changed 9 years ago by
Milestone: | sage-6.1 → sage-6.2 |
---|
comment:7 Changed 9 years ago by
Milestone: | sage-6.2 → sage-6.3 |
---|
comment:8 Changed 8 years ago by
Milestone: | sage-6.3 → sage-6.4 |
---|
comment:9 Changed 8 years ago by
Reported "upstream" at https://github.com/sagemath/sagenb/issues/221
comment:10 Changed 2 years ago by
Cc: | Frédéric Chapoton added |
---|---|
Milestone: | sage-6.4 → sage-duplicate/invalid/wontfix |
Status: | needs_work → needs_review |
Proposing to close all sagenb tickets as outdated, so that all remaining open tickets in the notebook component are about the Jupyter notebook.
comment:11 Changed 2 years ago by
Resolution: | → invalid |
---|---|
Status: | needs_review → closed |
Note: See
TracTickets for help on using
tickets.
Added a development section. Replaces the last patch