Typically the score of a code challenge is based off of the total passed test cases divided by the total number of test cases. This means by default, a challenge score is a "completion score". However there are options you can use to configure test cases to enable more advanced scoring. This article will briefly walk you through your options.
A weighted test case is when you give more weight to certain unit test cases. For example, you may have 3 test cases, but you want one of those test cases to count for 50% of the score. You could give that test case a weight of
2 so that it is worth twice as much.
You can read more about weighted test cases within our reference docs.
Beyond the score percentage, you can also break down a challenge into sub-scores. For example, a challenge may have 10 test cases. Two of those test cases may be related to how well a candidate handles edge cases. You could tag those two unit tests with "Edge Cases". In addition to the overall percentage score, you would also see a breakdown of how many edge case tests the candidate completed.
You can define as many tagged test cases as you want, and assign multiple tags to each case.
You can read more about tagged test cases within our reference docs.