Fix#392

[kurahaupo]

What does this implement/fix? Please describe.
Display the "uptime" in beacons in better human-readable format.

Does this close any currently open issues?
#392

[kurahaupo]

fixes #392

[kurahaupo]

Oh dear, I've just realised this has been sending email for every pushed commit, and triggering the unit tests. Sorry about that.

I'm puzzled as to why JaCoCo now fails, when (as far as I know) I've added test coverage for all of my additions.

[VREMSoftwareDevelopment]

Please merge the latest feature branch into fix#392

[VREMSoftwareDevelopment]

Please take a look starting at build->coverage-4446

"Rule violated for bundle app: complexity covered ratio is 0.87, but expected minimum is 0.88"

It is not code coverage, it is new added code complexity.

[kurahaupo]

I made a specific point of adding tests, so this report is really confusing.

How is "added code complexity" computed?

Is there a penalty for code laid out in a tabular arrangement like "too many statements per line"?

[kurahaupo]

I wonder if the coverage tool is getting confused by having two scale measures over the same variable, and thinking they need M+N tests (or even M×N) when in fact the intentional interleaved scales mean that the actual number of tests to have full coverage is significantly fewer, basically max(M,N)+1.

I don't want to wind up with code that's harder to read just to get it to pass a metric.

[VREMSoftwareDevelopment]

I don't want to wind up with code that's harder to read just to get it to pass a metric.

• JaCoCo ->Documentation -> Coverage Counters Cyclomatic Complexity section
• Wikipedia Cyclomatic Complexity "Cyclomatic complexity is a software metric used to indicate the complexity of a program"
• Wikipedia Programming Complexity "Higher levels of complexity in software increase the risk of unintentionally interfering with interactions and so increases the chance of introducing defects when making changes"