aboutsummaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Removed the configs.Tiago Serafim2012-09-081-10/+1
|
* Initial version with insufficient tests and no docs.Tiago Serafim2012-09-024-10/+85
|
* Merge commit '63020032eab733ed74f06a687abb5c358de4e931'Dmitry Shachnev2012-08-261-1/+0
|\
| * Don't import from doctest, it's no longer usedDmitry Shachnev2012-08-261-1/+0
| |
* | Fix `footnote_many_footnotes` test as per #129Dmitry Shachnev2012-08-251-2398/+2398
|/
* Fixed #129. Footnotes now output valid HTML5.Waylan Limberg2012-08-093-15/+15
| | | | | | | | | | | | | | | | As HTML5 has depreciated use of `rev=anything` and `rel=footnotes`, they are no longer inlcuded in the output when the output_format is set to HTML5. Note that if someone successful registers a spec for `rel=footnotes` in the future (as a microformat), then that could be considered valid. But until that happens, it is invlaid to use in HTML5. Therefore, we remove it from the output (when outputing HTML% only). As an alternative, two new classes are set (in all output_formats). On the link to the footnote (where `rel=footnotes` was used), we set `class=footnote-ref` and on the backlink (where `rev=footnote` was used), we set `class=footnote-backref`. Also updated the tests to reflect to the new classes in the output.
* Fixed #114. Converted doctests to unittests. While I left the doctests there ↵Waylan Limberg2012-07-261-0/+275
| | | | for documentation purposes, they are no longer being run. Perhaps I'll delete them later and add links to the online docs or something.
* Added support for <foo>+<bar> lexers of Pygmentspapaeye2012-07-212-0/+20
|
* Fixed #115. Make sure all file objects are closed.Waylan Limberg2012-07-121-2/+5
|
* Fixed #112 and cleaned up error reporting when loading extensions.Waylan Limberg2012-07-121-3/+3
|
* Fixed #106. Replaced all references to freewisdom.org (except for Yuri's ↵Waylan Limberg2012-06-284-24/+24
| | | | homepage).
* Add test for 5236a9838c580a17c3299efb97d9f41ce2a1efabCatalin Iacob2012-04-173-0/+7
|
* tests for 9852c2263ef7775d2a508a9c1721148cbf3ae258fin2012-04-112-0/+2
|
* Fixed #85. Odict now handles link errors correctly.Waylan Limberg2012-03-191-0/+8
| | | | Also added a test. Thanks for the report.
* Fixed #78. Added support for two line link refs.Waylan Limberg2012-02-022-1/+7
| | | | | Also refactored the reference preprocessor to make this a little easier to implement. Regex does more now.
* Fixes #64. Added sane_list extension.Waylan Limberg2012-01-243-0/+40
| | | | | | | | | | This is an extension which alters the behavior of lists to be less surprising. If turned out to be rather simple to code. I'm surprised no one had written it yet. I should note that this extension does not generate separate lists if different unordered list markers are used (`*` verses `-` verses `+`) The way the parser works that would be a little more tricky.
* Removed Codehilite from tests.Waylan Limberg2012-01-202-32/+32
| | | | | | Codehilite generates differant output with differant versiosn of pygments. We support those various versions of pygments but can't unsure that the same version is always available on every platform tests are run on.
* It is spelled 'serializers' not 'searializers'.Waylan Limberg2012-01-201-7/+7
|
* Inline html is now escaped by the searializer.Waylan Limberg2012-01-196-7/+7
| | | | | | | | Final fix to issue introduced in fix for #59. Weird stuff inside angle brackets now also work in safe_mode='escape'. We just did the same thing as with block html, let the (x)html searializer do the escaping. Tests updated including the standalone test moved to match the non-escape cases.
* Partial fix for issue introduced in fix for #59Waylan Limberg2012-01-196-1/+8
| | | | | Markdown markup inside angle bracktes now gets rendered properly in all cases except when safe_mode='escape'. Also added tests.
* Cleaned up tests after merging pull request fixing #72.Waylan Limberg2012-01-185-3/+0
|
* Support github-flavored markdown by making the '.' optional before language ↵Mike Dirolf2012-01-173-0/+69
| | | | type.
* Fenced code blocks need to end with a fence on its own line.Mike Dirolf2012-01-173-0/+69
|
* When safe mode is 'escape', don't allow bad html to stop further processing.Mike Dirolf2012-01-144-21/+28
| | | | | | | | | | See tests/html4_safe/html_then_blockquote.(txt|html). It looks like having unclosed block-level html elements was causing further processing not to happen, even in the case where we're escaping HTML. Since we're escaping HTML, it seems like it shouldn't affect processing at all. This changes output results in a couple of other tests, but the new output seems reasonable to me.
* Fixed #68. Blank line is not required after html comments.Waylan Limberg2012-01-153-2/+12
| | | | | Interestingly, the change to the misc/mismatched-tags test is inline with PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
* Fixed #57. Multiline HTML Blocks no longer require a blank line after them.Waylan Limberg2012-01-153-2/+17
|
* attempt at a fix for issue w/ MD links inside of html tagish stuff with safe ↵Mike Dirolf2012-01-123-0/+5
| | | | mode on.
* also undo changes to the test.cfgDaniel Gottlieb2011-12-271-4/+0
|
* appropriately move the tests to the fenced code documentation in the ↵Daniel Gottlieb2011-12-272-150/+0
| | | | extension source
* Allow tildes or backticks in the fenced_code extension to support the syntax ↵Daniel Gottlieb2011-12-273-1/+155
| | | | used by github
* Some more tests for issue #51. An upate to Marcin Kasperski's tests (which I ↵Waylan Limberg2011-11-173-2402/+1212
| | | | previously merged). Thanks Marcin. Also added a test for not-indented secondary lines of a first paragraph in a footnote definition.
* Merge git://github.com/Mekk/Python-Markdown into mekkWaylan Limberg2011-11-172-0/+10796
|\
| * Example test for #51 (crash on docs with +1000 footnotes)Marcin Kasperski2011-11-102-0/+10796
| |
* | Fixed #51. Removed recussion from footnote preproccessor. Also refactors the ↵Waylan Limberg2011-11-183-14/+7
| | | | | | | | code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
* | Fixed #47. Improved HRProccessor.\n\nPython's re module does not support ↵Waylan Limberg2011-11-172-1/+7
|/ | | | atomic grouping, which was slowing the HR regex down if a long HR ended with a non HR char (casing the regex to backtrack). Therefore, we have to simulate atomic grouping. Fortunately, we only need to match end-of-line or end-of-string after the atomic group here, so it was an easy case to simulate. Just remove the '$' from the end of the regex and manualy check using m.end(). The run method was refactored while I was at it, saving us from running the regex twice for each HR.
* No longer skipping all tests from PHP test suite. We skip some because PHP ↵Waylan Limberg2011-10-061-1/+38
| | | | differs from markdown.pl and we match markdown.pl. A few others are skipped because we have to adjust for a few edge cases. See comments in tests/php/test.cfg for details.
* Skipped 3 failing pl tests with some weird edge cases. A significant rewrite ↵Waylan Limberg2011-10-061-0/+12
| | | | if inlinepatterns will probably be needed for this. Putting it on hold till after 2.1-final is released.
* Run a few more pl tests. Some of them are failing but should be easily fixable.Waylan Limberg2011-08-272-0/+12
|
* Added greater-than as an escaped character. Apparently markdown.pl escapes ↵Waylan Limberg2011-08-272-0/+3
| | | | it even though it is not documented.
* Fixed #39. Refactored escaping so that it only escapes a predifined set of ↵Waylan Limberg2011-08-172-3/+0
| | | | chars (the set defined by JG in the syntax rules). All other backslashes are passed through unaltered by the parser. If extensions want to add to the escapable chars, they can append to the list at markdown.ESCAPED_CHARS.
* Added some fadfile commands to (re)generate tests when they are added or ↵Waylan Limberg2011-08-041-5/+38
| | | | updated.
* TestCase.assert_ and TestCase.failUnless are depreciated in Python 3 in ↵Waylan Limberg2011-07-281-3/+3
| | | | favor of testCase.assertTrue. Might as well be using the right method in our tests.
* Skip the UnidoceDecodeError API test in Python 3.x as all input should be ↵Waylan Limberg2011-07-281-2/+3
| | | | unicode anyway.
* Python 3.2 made some changes to the configparser which broke the testing ↵Waylan Limberg2011-07-282-5/+5
| | | | framework. With a simple addition to our subclass (which we then make use of), this is an easy fix.
* Fixed a Python 2.4 incompatability in last commit. 'encode' only accepted ↵Waylan Limberg2011-07-281-1/+1
| | | | positional arguments back then.
* All internal encoding of output now uses the 'xmlcharrefreplace' error ↵Waylan Limberg2011-07-281-1/+1
| | | | handler. Also added a note to the docs. Anyone doing their own encoding of output should be as well.
* All API tests now utilize our own searializers.Waylan Limberg2011-07-271-3/+5
|
* Fixed #31. Headers in tight lists now get inline patterns run on their ↵Waylan Limberg2011-07-212-4/+4
| | | | tails. Tests included.
* Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵Waylan Limberg2011-06-292-1/+62
| | | | Thanks to skurfer for report and inital patch.
* Fixed #28. Inline raw html is now enclosed in p tags. This used to work. ↵Waylan Limberg2011-06-283-2/+4
| | | | Somehow we stopped checking for a single inline html element when swapping back in raw html. Added a test. Also patched a weird (invalid) comment test. Seeing the input is not really a valid html comment - it doesn't matter what we do with it. I suppose we test it to make sure it doesn't break the parser. Actual output is not so important. As a side note, this has exposed a preexisting (unrelated) bug with the extra extension's handling of raw html. That test is failing following this fix.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 05:11:16 +0000