tag:help.appveyor.com,2012-11-13:/discussions/suggestions/509-tests-badgeAppVeyor: Discussion 2018-10-19T08:16:56Ztag:help.appveyor.com,2012-11-13:Comment/356178322014-12-23T19:07:23Z2014-12-23T19:07:23ZTests badge<div><p>Nice idea, thanks!</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/356178322014-12-27T09:27:01Z2014-12-27T09:27:01ZTests badge<div><p>+1</p>
<p>A solution is also possible via the AppVeyor REST API since it
provides test-result information. It's not as nice as the existing
one-line badge for build results, but it already works well. The
main issue at least in my case was that GitHub blocked javascript
in markdown, so the best I could come up with was to forward the
badge request through a Web API:<br>
<a href=
"https://github.com/mmaitre314/TestStatusBadge">https://github.com/mmaitre314/TestStatusBadge</a></p></div>Matthieu Maitretag:help.appveyor.com,2012-11-13:Comment/356178322015-11-04T04:20:35Z2015-11-04T04:20:35ZTests badge<div><p>+1</p>
<p>I have tests for obscure corner cases and functionality not even
written yet (better than having TODOs). Project builds fine though,
yet I get a failed badge :(</p></div>Max Torotag:help.appveyor.com,2012-11-13:Comment/356178322015-11-26T11:34:57Z2015-11-26T11:34:57ZTests badge<div><p>+1000</p></div>Tanielian V. Barreiratag:help.appveyor.com,2012-11-13:Comment/356178322016-02-05T15:01:08Z2016-02-05T15:01:09ZTests badge<div><p>+1 I would love to have this.</p></div>Alexandre Robatag:help.appveyor.com,2012-11-13:Comment/356178322016-04-02T17:53:17Z2016-04-02T17:53:17ZTests badge<div><p>+1</p></div>Bruno Garciatag:help.appveyor.com,2012-11-13:Comment/356178322016-08-27T09:30:31Z2016-08-27T09:30:31ZTests badge<div><p>+1000 I love it. Many thanks</p></div>Marloxo