#9673 closed enhancement (fixed)
Referring to flag for doc-testing only changed files
| Reported by: | jsrn | Owned by: | mvngu |
|---|---|---|---|
| Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
| Component: | documentation | Keywords: | doctest |
| Cc: | chapoton | Merged in: | |
| Authors: | Reviewers: | Frédéric Chapoton | |
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Status badges
Description
In the Developer's Guide there is no reference to the "-tnew" flag to the sage executable, which will instruct Sage to only doctest changed files. I suggest adding such a reference in "Walking through the development process" as well as "Parallel Testing the Sage Library".
Change History (6)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Of course, the above shouldn't say "its dependencies" but rather "the files depending on them".
comment:3 Changed 5 years ago by
- Cc chapoton added
- Milestone set to sage-duplicate/invalid/wontfix
- Status changed from new to needs_review
This has been done, see http://doc.sagemath.org/html/en/developer/doctesting.html#testing-changed-files, so I suggest this one to be closed. Frédéric, please click positive_review if you agree.
comment:4 Changed 5 years ago by
- Reviewers set to Frédéric Chapoton
- Status changed from needs_review to positive_review
comment:5 Changed 5 years ago by
- Resolution set to fixed
- Status changed from positive_review to closed
comment:6 Changed 5 years ago by
Note: See
TracTickets for help on using
tickets.
Does anyone know how the "-tnew" flag works in detail? In particular, does it doctest every file that has been changed as well as its dependencies? If it is the case, this should be mentioned in the documentation. Otherwise, shouldn't it?