Why was the test "@checkNumberRecycling_C02.02_phone_number_not_found" removed from the test plan?

[fernandopradocabrillo]

Hi all!
I didn't realize that the test "@checkNumberRecycling_C02.02_phone_number_not_found" was removed from the test plan. I'm checking the PR conversation and the minutes of that meeting but I don't understand the reason.

Why is it not applicable for this API? We are reviewing the test plan internally and we doubt what to return in a 2-legged scenario when the API is invoked with a phoneNumber unkown for the Operator. For 3-legged it would not apply as the client needs to obtain a token and for that they need a phone number from the company.

Thanks!!

cc: @Masa8106

[Masa8106]

@fernandopradocabrillo , thank you for opening this discussion.

The reason why the test case "C02.02" was removed from Fall25 release is that we couldn't reach a consensus on how test condition is described by the deadline of Fall25 release.

I think we can revisit to discuss the test case "C02.02" for next release. So far, I believe it is preferable to create test scenarios that adhere to the commonalities guidelines as much as possible.

[fernandopradocabrillo]

thanks @Masa8106

As we discussed in the meeting on tuesday 11th I think this test should be included as it is defined in the Commonalities artifact. If there is any discussion about it should be placed there as this is the same for all CAMARA APIs.

[Masa8106]

I opened an issue related to this discussion.
So let me close this discussion. Thank you.