[PATCH i-g-t 2/2] tests/intel/kms_test_config: Add mandatory fields

[Swati Sharma <swati2.sharma@intel.com>]

To maintain consistency across all KMS test documentation, lets
make few fields mandatory.
Let's follow the following pattern

	/**
	  * TEST: <test name>
	  * Category: Display
	  * Description: <test description>
	  * Driver requirement: <i915/xe/i915, xe>
	  * Mega feature: <mega feature name>
	  *
	  * SUBTEST: <subtest name>
	  * Description: <subtest description>
	 */
TODO: Upstream documentation for mega feature

Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
---
 tests/intel/kms_test_config.json | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tests/intel/kms_test_config.json b/tests/intel/kms_test_config.json
index e11c7f4fe..aeb16a94b 100644
--- a/tests/intel/kms_test_config.json
+++ b/tests/intel/kms_test_config.json
@@ -28,10 +28,12 @@
             },
             "Category": {
                 "_properties_": {
+		    "mandatory": true,
                     "description": "Contains the major group for the tested functionality 'Display'"
                 },
                 "Mega feature": {
                     "_properties_": {
+			"mandatory": true,
                         "description": "Contains the mega feature for end to end use case, e.g. the 'PSR' feature."
                     },
                     "Functionality": {
@@ -44,6 +46,7 @@
         },
         "Driver requirement": {
             "_properties_": {
+		"mandatory": true,
                 "description": "Describes any Driver specific requrirement, like i915/xe."
             }
         },
@@ -59,6 +62,7 @@
 	},
         "Description": {
             "_properties_": {
+		"mandatory": true,
                 "description": "Provides a description for the test/subtest."
             }
         }
-- 
2.25.1