Opened 12 years ago

Closed 18 months ago

#8754 closed enhancement (invalid)

sagenb -- add "how to test" directions to the sagenb README.txt

Reported by: was Owned by: jason, was
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: notebook Keywords:
Cc: chapoton Merged in:
Authors: William Stein, Alex Leone Reviewers: William Stein
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

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)

trac_8754-sagenb.patch (1.2 KB) - added by was 12 years ago.
trac_8754-sagenb.2.patch (2.5 KB) - added by acleone 12 years ago.
Added a development section. Replaces the last patch
trac_8754-sagenb.replaces2.patch (3.3 KB) - added by acleone 12 years ago.
Newest Version. Added a "Reviewing Patches" section. Apply only this.

Download all attachments as: .zip

Change History (14)

Changed 12 years ago by was

comment:1 Changed 12 years ago by was

  • Status changed from new to needs_review

comment:2 Changed 12 years ago by was

  • Status changed from needs_review to positive_review

Changed 12 years ago by acleone

Added a development section. Replaces the last patch

comment:3 Changed 12 years ago by acleone

  • Authors set to William Stein, Alex Leone
  • Reviewers set to William Stein

Changed 12 years ago by acleone

Newest Version. Added a "Reviewing Patches" section. Apply only this.

comment:4 Changed 12 years ago by mpatel

  • Status changed from positive_review to needs_work

Should someone review the latest patch? I noticed two minor problems:

  • dwnload
  • An extra * in b) * 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 8 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:6 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:7 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:8 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:9 Changed 7 years ago by kcrisman

comment:10 Changed 18 months ago by mkoeppe

  • Cc chapoton added
  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
  • Status changed from needs_work to 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 18 months ago by chapoton

  • Resolution set to invalid
  • Status changed from needs_review to closed
Note: See TracTickets for help on using tickets.