Skip to content

Test Scenario 3: Create and test a new rule based upon the "CNIC" field #621

@Behjet-A

Description

@Behjet-A

Pre-requisites:
Due to the unavailability of ConfigUI, we need to manually create and add the configurations into database before creating new rules.

  1. Add config in RuleConfig with different bands on cnic field. These bands will ensure that if the cnic in incoming request is found in the proscribed_cnic table then it should be interdicted.
  2. Add typology for that rule
  3. Update network_map

As a Maker,

  1. I will create a new rule in Rule Builder UI that will run the evaluations based upon the "cnic" field. This rule should be using the Query Node.
  2. I will add the test cases using the Test Cases generation tab
  3. I will deploy the rule in Simulation Sandbox environment (37)
  4. I will verify the Test Report to ensure that all test cases are successful
  5. I will execute the rule using the "Single Rule" execution in Simulation tab
  6. I will execute the rule using the "End to end" execution
  7. Once everything is verified, send this rule for approval.

As a Checker,

  1. I will view the rule that is in Under Review status
  2. I will run the simulations (if needed), view the execution logs etc. and Approve the rule

As a Tester (on Simulation Sandbox (37)),
A rule should be deployed and available for End to End testing in Simulation Sandbox environment.
I will send the request to DEMS and check the evaluation results in evaluation table for the relevant message id.

As a Deployer,

  1. I will view the rule that is in "Approved" status.
  2. I will deploy the rule to the "Live" environment (34).

As a Tester (on Live environment (34)),
A rule should be deployed and available for End to End testing in Live environment.
I will send the request to DEMS and check the evaluation results in evaluation table for the relevant message id.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions