test coverage numbers are out of whack when the config file points to multiple accomplishments directories

Bug #1032459 reported by Matt Fischer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Accomplishments Battery
New
Low
Unassigned

Bug Description

When you run the battery and your config file points to more than one accomplishments directory, you get a coverage number of 50% (and 2 Scripts). Only 1 script is ever run, presumably the first one in the path, and the coverage should be 100%

Config File:
[config]
...
accompath = /home/mfisch/experiments/accomps/ubuntu-community-accomplishments/master:/usr/share/accomplishments

Output:
mfisch@caprica:~/experiments/accomps/ubuntu-community-accomplishments/master/tests/ubuntu-community$ accomplishments-battery -s ubuntu-community/attend-uds
Getting Accomplishment Data...
['/home/mfisch/experiments/accomps/ubuntu-community-accomplishments/master', '/usr/share/accomplishments']
Running: ubuntu-community/attend-uds for SUCCESS
...pass
Running: ubuntu-community/attend-uds for FAILURE
...pass
----- RESULTS -----
Total Scripts: 2
Total Scripts Run: 1 (0 scripts exempted)
Test Coverage: 50.00%

Failures:
 * None. :-)

Test Exemptions:
 * None. :-)

Missing Tests:
 * None. :-)

Matt Fischer (mfisch)
Changed in ubuntu-accomplishments-battery:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.