Let the PU-stub return a generic response for unknown persons

[albinsunnanbo]

When testing with the PU-stub using person numbers not included in the PU-Stub the stub currently returns Sökt_person_saknas_i_registren (0001).
This makes it problematic to use the stub for processing large amounts of data with different numbers.

Proposed solution is to always return Tjänsten_utförd (0000) and the verbatim text "Förnamn", "Efternamn" as first and last name.

Reserve specific obvious invalid numbers for testing the possible error codes.
I.e.
00019999999x for returning return code 0001
00209999999x for returning return code 0020
etc.

Any suggestions? @jonaskentor @johansvard @tomassarnhammar

[johansvard]

I think you will need to have at least one of each with a valid number, that does not exist.
Most Ui's will probalby not allow a faulty number to be sent at all...

[albinsunnanbo]

Can we find "valid" numbers that are not actual real numbers?

Another idea is to embed error codes in the URL
Like pu-stub/0020/?PKNODPLUS=xxxxxxxxxxxzz
But that would make it hard to test from an end user perspective

[albinsunnanbo]

I made an implementation that always returns a valid response regardless if the number is known or not
Replace "snod" with "SnodWithFakeUnknown" in the URL.
Instead of
http://pu-stub.azurewebsites.net/snod/PKNODPLUS?arg=191212121212
use
http://pu-stub.azurewebsites.net/SnodWithFakeUnknown/PKNODPLUS?arg=191111111111

It would also be possible to implement a similar "SnodWithErrorCodes", that returns the last four digits as the ReturnCode, making it possible to craft a "valid" number for each possible return code.

cc @jonaskentor