Unittests!
Boudewijn Rempt <[email protected]>
| Newsgroups | gmane.comp.kde.devel.koffice |
|---|---|
| Organization | valdyas |
| Message-ID | <[email protected]> |
For Krita, I've the habit of sending out a weekly mail with all tests that fail. Here's the same for all of KOffice:
The following tests FAILED:
10 - kword-part-TestRdf (Failed)
13 - kformula-LoadAndSave (Failed)
19 - KPlato-EstimateTester (Failed)
30 - kspread-Formula (Failed)
50 - kspread-Sheet (Failed)
80 - krita-image-KisConvolutionPainterTest (Failed)
170 - krita-plugin-format-jpeg_test (Failed)
213 - kotext-odf-TestLoading (Failed) (this one fails because i haven't qtscript installed. I guess it would fail even if I had).
272 - kchart-TestCellRegion (Failed)
278 - shapes-text-TestDocumentLayout (Failed)
279 - shapes-text-TestChangeListCommand (Failed)
284 - shapes-text-TestTextTool (Failed)
285 - shapes-text-TestChangeTrackedDelete (Failed)
286 - kspread-xlsx-FormulaParser (Failed)
Note that failing unittests are release blockers. That is, if this list isn't empty, we cannot release 2.3.
KSpread, KPresenter and KWord are contuously tracked on http://158.36.191.251:8080/. You can even see who causes regressions with which commits...
If you want to add the information to akregator, here's a full rss url:
http://158.36.191.251:8080/guestAuth/feed.html?itemsType=builds&buildStatus=successful&buildStatus=failed&itemsType=changes&userKey=guest
Next week, I'm going to try to figure out how to extend this build server with the rest of KOffice and make it send out "you broke the build/test" mails to koffice-devel.
--
Boudewijn Rempt | http://www.valdyas.org
Ceterum censeo lapsum particulorum probae delendum esse