Open j340m3 opened 5 years ago
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.
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?
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 =)
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?
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.
Nice. Now I have easy access to the build logs. Like it!
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?