Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some greentea warnings about summary miscount for assumption tests #5

Closed
screamerbg opened this issue Oct 14, 2016 · 2 comments
Closed

Comments

@screamerbg
Copy link
Contributor

screamerbg commented Oct 14, 2016

Target: All
Toolchain: ARMCC5

mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'OK'
mbedgt: test on hardware with target id: 07770221075469163810FF5C
mbedgt: test suite 'tests-assumptions-analogin' ...................................................... OK in 10.82 sec
        test case: 'AnalogIn - can co-exist with DigitalOut' ......................................... OK in 0.07 sec
        test case: 'AnalogIn - existence of `DEVICE_ANALOGIN` macro' ................................. OK in 0.08 sec
        test case: 'AnalogIn - pin can do DigitalOut' ................................................ OK in 0.07 sec
mbedgt: test case summary: 8 passes, 0 failures
mbedgt: utest test case summary mismatch: utest reported passes and failures miscount!
        reported by utest: passes = 8, failures 0)
        test case result count: passes = 3, failures 0)
@screamerbg screamerbg changed the title Some greentea warnings about summary miscount Some greentea warnings about summary miscount for assumption tests Oct 14, 2016
@BlackstoneEngineering
Copy link
Contributor

Right, thats because of this

Case cases[] = {
    Case("AnalogIn - existence of `DEVICE_ANALOGIN` macro", Macro_Test,greentea_failure_handler),
    Case("AnalogIn - pin can do DigitalOut", can_digitalout<MBED_CONF_APP_AIN_0>,greentea_failure_handler),
    Case("AnalogIn - pin can do DigitalOut", can_digitalout<MBED_CONF_APP_AIN_1>,greentea_failure_handler),
    Case("AnalogIn - pin can do DigitalOut", can_digitalout<MBED_CONF_APP_AIN_2>,greentea_failure_handler),
    Case("AnalogIn - pin can do DigitalOut", can_digitalout<MBED_CONF_APP_AIN_3>,greentea_failure_handler),
    Case("AnalogIn - pin can do DigitalOut", can_digitalout<MBED_CONF_APP_AIN_4>,greentea_failure_handler),
    Case("AnalogIn - pin can do DigitalOut", can_digitalout<MBED_CONF_APP_AIN_5>,greentea_failure_handler),
    Case("AnalogIn - can co-exist with DigitalOut", Can_AnalogIn_and_DigitalOut,greentea_failure_handler),

};

Each test needs a unique name, otherwise greentea overwrites them. I believe tests are printed out alphabetically by their description. So instead of all the tests having "AnalogIn - pin can do DigitalOut" they each need a unique name. Will fix and push shortly.

@BlackstoneEngineering
Copy link
Contributor

Change pushed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants