[Discussion] Automated test results/informations

[j340m3]

I don't find the README.md very informative. Since there is a travis.yml I suppose you're already using travis-ci. Why not publish the results?

1. I would like to have a badge showing the build status of the main branch or a link to the build results on travis.
2. We could also use coveralls or similar tools to display the code coverage.

[j340m3]

Also check out cookiecutter. There are some ways to get all the automations you may need by running a small script and inserting this repo into it.

[CRImier]

I see. It's just always been weird to me - the "100%: passing" labels the like, I suppose, people want to know there are tests and they are passing? =D Code coverage would be interesting, of course - but I'm sure it's pretty low, most of the apps are not covered by tests and at the moment it's not easy to do so. For now, I only add tests when I find a bug or add code in UI elements, so I wager the coverage isn't that high.

So, we now have Codecov integration - for now, in the devel branch. Will look into labels now - however, I also think this raises a bigger question, is our README good enough? Is there something we could add? Say, screenshots, contribution intro for beginners?

[CRImier]

Added badges in devel

[CRImier]

Important part - we're also using tests for UI "OTA" updates, our updater uses tests as a marker that it's safe to update the UI and rolls back the updates if tests fail =)

[j340m3]

I see. It's just always been weird to me - the "100%: passing" labels the like, I suppose, people want to know there are tests and they are passing? =D Code coverage would be interesting, of course - but I'm sure it's pretty low, most of the apps are not covered by tests and at the moment it's not easy to do so. For now, I only add tests when I find a bug or add code in UI elements, so I wager the coverage isn't that high.

So, we now have Codecov integration - for now, in the devel branch. Will look into labels now - however, I also think this raises a bigger question, is our README good enough? Is there something we could add? Say, screenshots, contribution intro for beginners?

• Screenshots are good attention catcher, but I'm usually to lazy to make them. And they have to be kinda meaningful. So I don't think that a booting screen would be enough. Way cooler would be an gif which shows some UI handling
• Contribution intro would be cool, but more like an abstract and then link to the whole dev documentation via a "learn more" link or such.
• Installation guide would also be helpful.
• Also maybe consider a "donation" section with a Paypal badge.

Important part - we're also using tests for UI "OTA" updates, our updater uses tests as a marker that it's safe to update the UI and rolls back the updates if tests fail =)

Then tests are even more important and describe also the robustness of the OTA process.

Added badges in devel

Nice. Now I have easy access to the build logs. Like it!

[CRImier]

• A gif sounds like a much better idea, indeed! Will look into it - likely, open a GH issue for now
• I'm thinking more of a "here's me making a simple contribution" tutorial, using emulator and all that. This I probably ought to make myself =) Docs are already linked in the README, though it's kind of a plain link, wonder if those links could be formatted better.
• Installation guide is already linked in README
• Will think about "donate" - ZeroPhone project has donation links in more suitable places already, not sure this project stands out enough. Also, IMO the README page is aimed more at looking-to-be contributors and app developers, not "people that are interested in the project and would like to support it financially".