Skip to content

Weight string in wrong format is processed as Weight value 1 #3

Description

@ppetersvx

Context:
When performing outcome processing with a assessment result, having a assessment test definition with a weight with an invalid weight value (for example 3,5 instead of 3.5), the resulting weight is converted to a weight of null.
The nullified weight is filtered out of the weight collection in the initialisation phase of the AssessmentTest class, see below:

image

Bug
When the assessment result outcome is returned, the weight is fallen back to the value of 1. The expectation was, that the weight had a fallback value of 0 or an exception was thrown (this should be analysed first for impact).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions