tag:help.appveyor.com,2012-11-13:/discussions/suggestions/195-filtering-for-tests-in-test-reportAppVeyor: Discussion 2018-10-19T08:16:31Ztag:help.appveyor.com,2012-11-13:Comment/326897922014-04-24T17:32:36Z2014-04-24T17:32:36ZFiltering for Tests in test report<div><p>That's clear test results page must be more "friendly" for large
projects. What testing framework do you currently use?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/326897922014-04-25T05:39:45Z2014-04-25T05:39:45ZFiltering for Tests in test report<div><p>I'm using XUnit. Our tests are heavy on numerical algorithms and
we use data theories quite a bit. Therefore it would be nice to
group all the theory tests by their parent test.</p>
<p>Another nice feature would be to click on a failing issue and
automatically create an issue to fix it under github issues with a
link back to the failing test. When that test goes green possibly
on the next run you could have an option to automatically change
the status to closed or flag it for review or something like
that.</p></div>bradphelantag:help.appveyor.com,2012-11-13:Comment/326897922014-04-25T17:54:49Z2014-04-25T17:54:49ZFiltering for Tests in test report<div><p>Grouping theory tests is non-trivial. From integration
standpoint it looks like xUnit is running the same test again (with
the same name). I think it could be "hacked" using reflection, but
this is not a few hours :)</p>
<p>I like the idea of integrating tests into GitHub flow, but maybe
one issue per all failed tests? What if 100 tests failed?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/326897922014-04-28T05:03:06Z2014-04-28T05:03:06ZFiltering for Tests in test report<div><p>It kind of depends on the failure. If 100 tests go from passing
to failing in a single checkin then it is <strong>most
likely</strong> that it is a single source of error. If however
there are 100 failing tests that have built up over time then you
might want to associate specific issues or milestones with that
test.</p>
<p>I think two cases should be handled</p>
<ul>
<li>generically create an issue and link the failing log in it's
entirety.</li>
<li>link a specific test case to a new issue.</li>
</ul>
<p>It may even be useful to link a passing test case to an issue if
it might be required to add more tests or something other of note
arises when review the tests.</p></div>bradphelantag:help.appveyor.com,2012-11-13:Comment/326897922014-07-16T14:00:14Z2014-07-16T14:00:15ZFiltering for Tests in test report<div><p>Is this something that is being worked on? We have 1986 tests
(MSpec and custom JavaScript test runner) and now there are 2
failing - I luckily happen to know which ones, but that is seldom
the case: ( <a href=
"https://ci.appveyor.com/project/Dolittle/bifrost/build/1.0.22">https://ci.appveyor.com/project/Dolittle/bifrost/build/1.0.22</a>
).</p></div>Einar Ingebrigtsentag:help.appveyor.com,2012-11-13:Comment/326897922014-07-16T14:08:05Z2014-07-16T14:08:05ZFiltering for Tests in test report<div><p>While a new test results page with better experience is being
planned I think showing failed first will do the current one a
little better.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/326897922014-07-16T14:36:11Z2014-07-16T14:36:12ZFiltering for Tests in test report<div><p>That would really help.</p>
<p>Other than that; love your service! Keep up the great work!<br>
—<br>
Sent from Mailbox</p></div>Einar Ingebrigtsentag:help.appveyor.com,2012-11-13:Comment/326897922014-07-17T08:39:27Z2014-07-17T08:39:27ZFiltering for Tests in test report<div><p>Update has been just deployed. Failed tests come first in test
results report.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/326897922014-07-17T08:42:42Z2014-07-17T08:42:43ZFiltering for Tests in test report<div><p>Wow!<br>
Great stuff!</p>
<p>Thanks a lot, this was really helpful!</p>
<p>Amazed at your responsiveness, keep up the great work!</p></div>Einar Ingebrigtsentag:help.appveyor.com,2012-11-13:Comment/326897922015-06-25T12:45:18Z2017-03-29T14:10:48ZFiltering for Tests in test report<div><p>It would be nice to have "Failed only" filter by default for tests<br>
And paging</p>
<p>Having 2k tests is really hangs the page...</p></div>chudiniatag:help.appveyor.com,2012-11-13:Comment/326897922017-01-29T02:52:56Z2017-01-29T02:52:56ZFiltering for Tests in test report<div><p>I have to second the request. from llya. We have close to 4k
tests in our test suite and the test page is unusable. I keep
getting error from chrome saying that the page has become
unresponsive and asking me if I want to kill it.</p>
<p>It would be great to ONLY show failed tests by default. Passing
tests are irrelevant in most cases. Are you planing on implementing
this feature at some point?</p></div>michaeltag:help.appveyor.com,2012-11-13:Comment/326897922017-01-29T02:53:29Z2017-01-29T02:53:29ZFiltering for Tests in test report<div><p>I'm on business travel - will be back on the 6th of February.
Won't be checking this email all that much.</p>
<p>Best regards,</p>
<p>Einar</p>
<h2><a name="" class="anchor" href="#"></a></h2>
<p>Jeg er p? jobbreise, tilbake 6. februar. Vil frem til da ikke
sjekke denne eposten noe saerlig.</p>
<p>Mvh,</p>
<p>Einar</p></div>Einar Ingebrigtsen