search

tanyqcollin / pe

0 stars 0 forks source link

Hard to Test add command with NRIC #3

Open tanyqcollin opened 1 week ago

tanyqcollin commented 1 week ago

Although there is dummy NRIC for test purpose that provided in DG, it is hard to test with multiple valid Singapore NRIC beyond the provided NRIC, I must ensure each NRIC that i want to use is a valid NRIC.

image.png

nus-se-bot commented 6 days ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Not enough NRIC test case in DG

There is not enough NRIC test case in DG for tester to test the speed when the product handling a large number of data. And there is also no link for tester to refer to what is a valid NRIC. A good test guide should contain rich information for testers to explore.

截屏2024-11-15 17.02.43.png

[original: nus-cs2103-AY2425S1/pe-interim#3989] [original labels: severity.Medium type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Stress testing is a very small scope. You are still able to test other features of the product with the list of NRICs we have provided.

We lowered the severity to low due to the above reasons that testers will only face this issue when stress testing.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FeatureFlaw`] - [x] I disagree **Reason for disagreement:** ![image.png](https://raw.githubusercontent.com/tanyqcollin/pe/main/files/405472fc-0cc5-4b4a-943d-0ffe02defd3a.png) Although there is five dummy NRIC provided in the DG, it did not change the fact that this feature is a hard to test feature. It is a hard to test feature because tester cannot independently verify whether the NRIC validation algorithm is correctly implemented during the PE, as the logic behind the validation is not documented in DG and tester not allowed to use website to verify it. Besides, we have no tools or method to generate additional valid NRIC for comprehensive testing, we were restricted to test the feature with the given NRIC. Thus, these limitation make it difficult to ensure thorough testing of the feature, should be considered as `feature flaw` instead of `documentation bug`.