Research unit testing #119

New issue

Closed

opened 2026-04-02 08:58:29 +00:00 by b24erika · 2 comments

b24erika commented

2026-04-02 08:58:29 +00:00

Collaborator

Strategies to write a unit test.
related to issue Research Testing #81

Strategies to write a unit test. related to issue Research Testing #81

b24johka self-assigned this

2026-04-02 08:59:03 +00:00

b24erika was assigned by b24johka

2026-04-02 08:59:41 +00:00

b24johka removed their assignment

2026-04-02 08:59:41 +00:00

b24erika commented

2026-04-02 09:10:25 +00:00

Author

Collaborator

Suggested coverage of unit testing.

Unit testing should cover logic checks, boundary checks, error handling and object checks.

Logic checks are to verify that the system performs correct calculations as well as checking all possible paths through the code.

Boundary checks are to test edge cases and invalid inputs. For example if an integer between 1 and 10 is expected you check number 10 (edge case) as well as 11 which is a invalid input.

Error handling is to ensure that the system handles errors correctly, is the user prompt to insert new input or does it crash?

Object checks is to ensure that the state of it is correctly updated after the code is executed.

Suggested coverage of unit testing. Unit testing should cover logic checks, boundary checks, error handling and object checks. Logic checks are to verify that the system performs correct calculations as well as checking all possible paths through the code. Boundary checks are to test edge cases and invalid inputs. For example if an integer between 1 and 10 is expected you check number 10 (edge case) as well as 11 which is a invalid input. Error handling is to ensure that the system handles errors correctly, is the user prompt to insert new input or does it crash? Object checks is to ensure that the state of it is correctly updated after the code is executed.

b24erika added the

Team 1

testing

needs review

labels

2026-04-02 09:14:08 +00:00

b24johka closed this issue

2026-04-02 09:38:36 +00:00