"Pranav Rajput" [email protected] wrote:

When considering edge cases (via custom tests) for the assessed lab, should I consider that the object references provided (for Union or Intersection classes, for example) as arguments when testing them could be null, or is that outside the scope of the assessed lab?

See the clarifications added to the lab sheet. You do not need to handle errors, as this is not a task given in the specification.

Also, for the Range and the Union/Intersection classes, do they need to have it actually compute the values (in Arrays or something similar) or is it enough to ensure the two methods being implemented in each of them (describe, contains) have their logic work as expected and tested in the provided tests?

If your code behaves as is required of it, that is sufficient. The specification does not impose any requirements on the internal workings and implementation details of your code. You are not required to use arrays.

Is there any reason you would have to explicitly compute the values? What problems could this cause? Would you code still work reasonably if I asked for Range(0, 1_000_000_000)? Consider these when making your decision.