How can we test attachments at each status? Would NHSE be able to set the status on uploaded documents, or provide test data?
For example, we can’t upload a doc that would result in a THREAT_DETECTED, and anything PENDING would normally only remain in that state for a very short period of time.
Hi Phil,
We will shortly be providing new comms regarding timelines for A42 testing in the path to live environments, as these have been slighly delayed - hopefully being sent out tomorrow. We will speak to the teams involved in this area, as I suspect this might be a question others may ask also. Please bear with us for now.
Some new updates available here
https://digital.nhs.uk/services/e-referral-service/api/updates-and-releases/roadmap/file-attachments
Hi Phil, It won’t be our intention to place files for partners to test as this would be complicated given the variations testing taking place.
It appears the most recognised way to do this is via an EICAR test file which can be quickly created via a particular string of text EICAR test file - Wikipedia - this is a widely recognised, safe approach
Hi Tony
Thank you for the suggestion. I will take a look at the details, which I believe will result in a Threats Found status, but how do we test Validation Failed and Pending statuses?
For pending in particular, we would need a file where the status doesn’t change. Without that, we’ll be unable to test the status specific process we are having to build to support this change.
Thanks
Phil
Hey Phil - are you okay with me marking this as solved - as team members are dealing with it seperately over email.
Hi Tony
I’m happy for this to be marked as solved - just for completeness, here’s the advice we’ve had:
“When we have switched on malware scanning as part of Release 2, there will be a way to test this in INT. The current date for this is 01 June 2026.
PENDING is a time-dependent state so you will have to ensure you are attempting to download a file while a scan is taking place.
VALIDATION_FAILED – You can place an attachment into this state by using one of the failure cases below:
Content type of the file is not supported
Content type of the file does not correlate with the file extension
File provided is too large and is not supported by e-RS“