Functional testing of the channel

1. Regulatory Concept & Core Standards

This video's topic is functional testing of the channel. By the end, you should be able to test receipt, response and protective safeguards. We will connect the information available, the criterion guiding the decision and the action that must be recorded. Follow the case and compare your answer with the proposed response. Audit compares criteria with evidence and reports findings within a defined scope. This course proposes an internal verification approach. It is not official certification or a guarantee that no wrongdoing exists. Access to reports must remain limited and justified during audit.

A working homepage does not establish a working process. Test submission, acknowledgement, follow-up, allocation and access. In Bulgaria, an anonymous scenario must test correct article 9 handling rather than represent anonymous statutory proceedings as available. A functional test is not a complete cybersecurity assessment.

Apply the following rule: For internal reports, acknowledge receipt within seven days of receipt. Give feedback on follow-up within three months after acknowledgement or, if none was sent, after expiry of the seven-day acknowledgement period: article 16, points 1 and 4. Do not substitute 90 days or the opening date. Externally, article 23 requires immediate acknowledgement, no later than seven days after receipt, with exceptions for an express request or risk to identity protection. Feedback is due within three months, extendable to six in duly justified cases requiring an in-depth investigation. The article 26 report is due within three or, as applicable, six months of receipt. The external extension does not apply to internal reporting.

2. Practical Implementation & Procedure

Obtain the required internal authorisation for testing and use fictional data in a training environment. Define expected outcomes and test deadlines, cover, conflicts and denial of unauthorised access. Do not copy real case files as evidence or send uncoordinated test reports to an organisation or authority. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.

3. Case Study & Compliance Action

Submission works, but the follow-up code cannot reopen messages. Testing finds a failure that checking the homepage alone would miss. The team records impact and requests correction and retesting of the affected journey. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.

The exercise is as follows: Is checking that the form opens enough to establish that the channel works? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.

No. Test the complete journey and relevant safeguards. The homepage is one point. The report must identify tested routes and results.

One mistake to avoid is: submitting uncoordinated fictional cases that can be mistaken for genuine reports.

Now apply the national rule to a second decision. The platform uses a fixed 90-day period for every country, starting when someone opens the message. Can this setting be retained?

Not without validating the local rule. Use the correct starting event and unit, distinguish acknowledgement from follow-up and allow only permitted extensions. Test receipt outside working hours, month-end dates and the responsible person's absence. Opening a message does not automatically change the legal date of receipt.