Given the following mockup and requirements, write a test plan to verify expected behavior and design of this interface.
Instructions Given the following mockup and requirements, write a test plan to verify expected behavior and design of this interface. Description In the Product there is a feature to exclude folders, files, or file types on selected end points (“Hosts”) from triggering a “Detect” (A flagged pattern on a “Host” that could be malicious in nature) and a “Block” (Blocking a file from executing). It can also exclude the folder, file, or file types from being extracted from the end users’ machine (“end point”) and uploaded to our Cloud to be quarantined. The following is a modal to add a new one of these “Exclusions”. Devalue user creates new file path exclusion to exclude from detections and/or extraction on all hosts. Goal: User can create new exclusion by targeting hosts, adding pattern, and choosing exclusion types Page/Place Requirement and acceptance criteria Content Add Exclusion modal Entry point: Add exclusion button on the File Exclusions page. From the Add Exclusion modal the user can set the following: · Targeted hosts · Defaulted to all hosts · Note: for the purpose of this exercise, a preceding modal to select Targeted hosts was removed and have chosen the default has been chosen already. · Exclusion pattern · User will use glob syntax as the pattern format. Link to glob syntax guidelines for reference. · Exclusion type · Detect/block: prevents files matching the exclusion pattern from triggering detections or blocks when on that host · File extraction: prevents files matching the exclusion pattern from being extracted and uploaded from quarantined files User can choose to test their exclusion pattern by inputting a sample file path and selecting “Test” action. Testing not required. User should not be able to create duplicate exclusions. User can optionally choose to check a box to immediately show a new exclusion form after saving. This will allow users to more quickly add multiple exclusions at a time. · When the checkbox is ticked, the user will see a notification and the text fields will clear so that the user can add another. · the focus will be on the exclusion pattern text field · They will be adding the exclusions to the same host groups previously selected. · By default, this checkbox will be unclicked. Exclusion added From the Add Exclusion modal the user will be able to click "Save" which will dismiss the modal and a success flash message will appear above the file path exclusion table. In the case the user checks “Save and add another” option, clicking “save” will save the current exclusion and clear the form back to its default state. Exclusion warning The user will be warned about dangerous patterns: · when a user types in ** in the Exclusion pattern field, show a warning flash message · If a user chooses both detect/Block and extraction and uses a pattern that has been blacklisted, the notification will display: 'Detect/Block can't be applied to [pattern entered], it will put your environment at risk' Instructions Given the following mockup and requirements, write a test plan to verify expected behavior and design of this interface. Description In the Product there is a feature to exclude folders, files, or file types on selected end points (“Hosts”) from triggering a “Detect” (A flagged pattern on a “Host” that could be malicious in nature) and a “Block” (Blocking a file from executing). It can also exclude the folder, file, or file types from being extracted from the end users’ machine (“end point”) and uploaded to our Cloud to be quarantined. The following is a modal to add a new one of these “Exclusions”. Devalue user creates new file path exclusion to exclude from detections and/or extraction on all hosts. Goal: User can create new exclusion by targeting hosts, adding pattern, and choosing exclusion types Page/Place Requirement and acceptance criteria Content Add Exclusion modal Entry point: Add exclusion button on the File Exclusions page. From the Add Exclusion modal the user can set the following: · Targeted hosts · Defaulted to all hosts · Note: for the purpose of this exercise, a preceding modal to select Targeted hosts was removed and have chosen the default has been chosen already. · Exclusion pattern · User will use glob syntax as the pattern format. Link to glob syntax guidelines for reference. · Exclusion type · Detect/block: prevents files matching the exclusion pattern from triggering detections or blocks when on that host · File extraction: prevents files matching the exclusion pattern from being extracted and uploaded from quarantined files User can choose to test their exclusion pattern by inputting a sample file path and selecting “Test” action. Testing not required. User should not be able to create duplicate exclusions. User can optionally choose to check a box to immediately show a new exclusion form after saving. This will allow users to more quickly add multiple exclusions at a time. · When the checkbox is ticked, the user will see a notification and the text fields will clear so that the user can add another. · the focus will be on the exclusion pattern text field · They will be adding the exclusions to the same host groups previously selected. · By default, this checkbox will be unclicked. Exclusion added From the Add Exclusion modal the user will be able to click "Save" which will dismiss the modal and a success flash message will appear above the file path exclusion table. In the case the user checks “Save and add another” option, clicking “save” will save the current exclusion and clear the form back to its default state. Exclusion warning The user will be warned about dangerous patterns: · when a user types in ** in the Exclusion pattern field, show a warning flash message · If a user chooses both detect/Block and extraction and uses a pattern that has been blacklisted, the notification will display: 'Detect/Block can't be applied to [pattern entered], it will put your environment at risk'