Add instructions for chef-cli validation (#4)

Add more clear instructions on how to make validation with chef-cli for
IDM and EDM

work item: https://app.devrev.ai/devrev/works/ISS-193822

Author: tjazerzen

devrev-trello-snapin.plain

@@ -88,6 +88,11 @@
 
 - Store The External Domain Metadata JSON object as a separate JSON file.
 
+
+***Test Requirements:*** 
+
+- The Conformance Tests should not modify nor do any transformations on The External Domain Metadata JSON object at all. If The Conformance Tests indicates a problem with The External Domain Metadata JSON object, The External Domain Metadata JSON object in the implementation code should be adjusted to fix the problem. The tests should only validate the JSON object in its original form.
+
 ***Functional Requirements:***
 
 - Implement The Function that generates and returns The External Domain Metadata JSON object. The record types that should be included in the The External Domain Metadata are The List of Cards ('cards') and The List of Users ('users').
@@ -99,6 +104,7 @@
     - The path to The Chef CLI executable is provided in the environment variables `CHEF_CLI_PATH`.
     - For the test to be successful The Chef CLI must return an empty output.
     - The test should always fail if The Chef CLI is not available.
+    - The Acceptance Tests should not modify nor do any transformations on The External Domain Metadata JSON object at all. The Acceptance Tests should just read The External Domain Metadata JSON object and pass it to The Chef CLI.
 
 
 ## Generate 'initial_domain_mapping.json'
@@ -112,22 +118,27 @@
   - Please note that mappings are split into separate ‘shards’ - one for each record type - for easier manipulation and storage.
   - Please note that a leaf type or a concrete id has to be selected for use_devrev_record, but not both.
 
+
 ***Non-Functional Requirements:***
 
 - Store The Initial Domain Mapping JSON object as a separate JSON file.
 
+***Test Requirements:***
+
+- The Conformance Tests should not modify nor do any transformations on The Initial Domain Mapping JSON object at all. If The Conformance Tests indicates a problem with The Initial Domain Mapping JSON object, The Initial Domain Mapping JSON object in the implementation code should be adjusted to fix the problem. The tests should only validate the JSON object in its original form.
+
 ***Functional Requirements:***
 
 - Implement The Function that generates and returns The Initial Domain Mapping JSON object.
 
-
   ***Acceptance Tests:***
 
   - Validate generated The Initial Domain Mapping JSON object with the chef-cli tool (The Chef CLI) using the command "chef-cli initial-mapping check -m <The External Domain Metadata JSON object file>":
     - The Chef CLI reads The Initial Domain Mapping JSON object from stdin.
     - The path to The Chef CLI executable is provided in the environment variables `CHEF_CLI_PATH`.
     - The test should always fail if The Chef CLI returns a non-empty output.
     - The test should always fail if The Chef CLI is not available.
+    - The Acceptance Tests should not modify nor do any transformations on The Initial Domain Mapping JSON object at all. The Acceptance Tests should just read The Initial Domain Mapping JSON object and pass it to The Chef CLI.
 
 
 ## Pushing data to DevRev servers