[CORE-75] Form Unit Test

[tiffanyfan1015]

Type of changes

• Feature

Purpose

• Add Question service test
• Add Response service test
• Add Submit service test
• fix: resolve date type, add continue in response service

Additional Information

1. Question service

• Create ->Known Type Success, Unknown Type Failed
• ListByFormID ->All Known Type return []Answerable, if one type unknown then fail

2. Response service

• CreateOrUpdate -> length → not same return error, Exists = true → Update, Exists=false → Create
• Update -> answer does not exist → create it, answer exists and same → nothing change, answer exists and not same → update

3. Submit service

• Submit -> All valid → CreateOrUpdate, some validate wrong → should not call CreateOrUpdate, if some answer.QuestionID not in list → error and not call CreateOrUpdate

[YukinaMochizuki]

I noticed that the Question service adopts table-driven testing, but Response and Submit do not. The current unit tests for Response and Submit suffer from low readability, which makes it difficult to quickly understand the intent of each test case. This will likely cause pain when modifying or adding test cases in the future.

Please at least adopt table-driven testing and include more failure cases to observe any unexpected behaviors, rather than only testing cases with valid formats. When using table-driven tests, please consider separating members such as name, param, setup, and validate, and make sure the name clearly describes the purpose of each test case.

For large mock (fake) structs, please use mockery to generate mocks. This helps maintain readability and future extensibility, while also reducing unnecessary boilerplate code, especially for methods that are not currently in use.

For the table-driven style, consider referring to unit_test.go.

[YukinaMochizuki]

For complex mock services, please use mockery.

[dytsou]

Some style issues have to be fix. Since Golang has a strict convention on naming, the abbreviated variables should be straighforward, or we often uses full names.

There are some similar cases in other lines that I have not listed below would also have to be fixed.