|
All JUnit tests for Marauroa [https://travis-ci.org/arianne/marauroa] and Stendhal [https://travis-ci.org/arianne/stendhal] are passing. So before we do a new release, we can just check there. In addition, Travis will execute the test suite for each pull request and post the result directly to the pull request page. Unfortunetelly there is nice output of failed tests. So in case of failures, we have to look at the console log or execute the tests locally.
Failed tests are reported to IRC again. We should add the [https://travis-ci.org/arianne/stendhal.svg build-passing image] and Github to [https://arianne-project.org https://arianne-project.org] and [[Stendhal Testing]].
Failed tests are reported to IRC again.
20:19kiheruWeWe should document pull requests on [[How To Create Patch For Stendhal]]. We can recommend pull requests, but accept patches as well. For those familiar with githubGithub pull requests are easy ,. butBut forpatches thoseare whosimpler arent,for patcvhesthe are likely simplerothers.▼<!--
* markus: I thought about doing sth like our junit history at work
20:18hendrikBut it would be the place to invoke postman from.
20:18balaurI also like the idea of pull requests more, but for a patch you don't need an account
20:18hendrikYes, that was the idea. But that's quite a bit of work. And it's kind of boring having to develop that again from scratch. So I postponed it.
20:19hendrikPerhaps we should point out both alternatives to new contributors. Or would that be too confusing?
▲20:19kiheruWe can recommend pull requests, but accept patches as well. For those familiar with github pull requests are easy, but for those who arent, patcvhes are likely simpler
20:19*hendrik nods.
20:19markusyes, kiheru.
20:20balauri agree
20:20hendrikMarkus is refering to our testresults datenbank at work. It basically consists of a table of test runs, a table of test names, and a table of results. The result table links the other two tables.
20:21markusso we should add that to https://stendhalgame.org/wiki/How_To_Create_Patch_For_Stendhal as alternative path.
20:21markusI am thinking about possibities for jenkins to be abused for that.
20:22hendrikSo we can make database queries such as: Which tests failed this time, but were fine on the last run? Or: On which test run did the failure straigh start for this test?
20:22hendrikWe have no jenkins.
20:23markusI know :) But: If we have a "publish-only-reports"-style job, such a jenkins would not waste too much resources
20:24hendrikThis has rather low priority for me, because I assume that we will fix failing tests quickly. Not keep a large number of test unfixed for a long time.
20:24markusJust an idea to get there. But maybe needs more thinking. :)
20:25markusRegarding travis: Can we get the build status prominent in some place?
20:26hendrikhttps://travis-ci.org/arianne/stendhal.svg
20:26markusI was more aiming on embedding that badge in one of our pages
20:27hendrikWhich page?
20:28markusarianne-project.org maybe?
20:28hendrikhttps://stendhalgame.org/wiki/Stendhal_Testing ?
20:28hendrikOn the left site?
20:28markusyes, good idea :)
20:29hendrikAnd a github logo.
20:29markusyes.
20:29kiherucan't hurt to have it there. not as good as screaming about failures at irc, but at least a place where somebody will notice it hopefully
20:30hendrikI think it is "both" not "one or the other".
20:30hendrikOn the website it's basically advertisment that we are doing good work[tm].
20:31hendrikOn IRC is were we will need it for practical reasons.
-->
|