Renaming end-to-end (E2E) tests to conformance tests to align ourselves with the nomenclature used by Tesll.

Author: dusano

.gitignore

@@ -3,9 +3,9 @@ __pycache__
 
 # Plain
 examples/**/build*/
-examples/**/e2e_tests/
+examples/**/conformance_tests/
 examples/**/node_build/
-examples/**/node_e2e_tests/
+examples/**/node_conformance_tests/
 examples/**/package-lock.json
 examples/**/node_modules/
 examples/**/node_harness_tests/

Plain-language-specification.md

@@ -146,12 +146,12 @@ Functional requirements are rendered incrementally one by one. Consequently earl
 
 ## Test Requirements
 
-The `***Test Requirements:***` specification is a list of instructions that steer implementation of end-to-end tests and provide details of testing environment.
+The `***Test Requirements:***` specification is a list of instructions that steer implementation of conformance tests and provide details of testing environment.
 
 Here's an example specification of test requirements.
 
 ```plain
-- End-to-end tests of The Program (The E2E Tests) should be implemented in Python using Unittest framework. 
+- The Conformance Tests of The Program should be implemented in Python using Unittest framework. 
 ```
 
 # Extended Syntax

README.md

@@ -57,8 +57,8 @@ To have the hash generated use the following command:
 ## Usage
 ```
 plain2code.py [-h] [--verbose] [--debug] [--base-folder BASE_FOLDER] [--build-folder BUILD_FOLDER]
-    [--render-range RENDER_RANGE] [--unittests-script UNITTESTS_SCRIPT] [--e2e-tests-folder E2E_TESTS_FOLDER]
-    [--e2e-tests-script E2E_TESTS_SCRIPT] [--api [API]] [--api-key API_KEY] filename
+    [--render-range RENDER_RANGE] [--unittests-script UNITTESTS_SCRIPT] [--conformance-tests-folder CONFORMANCE_TESTS_FOLDER]
+    [--conformance-tests-script CONFORMANCE_TESTS_SCRIPT] [--api [API]] [--api-key API_KEY] filename
 
 Render Plain source to software code.
 
@@ -80,11 +80,11 @@ options:
   --unittests-script UNITTESTS_SCRIPT
                         Name of a shell script to run unit tests. The script will receive
                         the build folder as its parameter.
-  --e2e-tests-folder E2E_TESTS_FOLDER
-                        Location of the folder where generated end-to-end test files will be written.
-  --e2e-tests-script E2E_TESTS_SCRIPT
-                        Name of a shell script to run end-to-end tests. The script will receive
-                        the build folder and the end-to-end tests subfolder as its parameters.
+  --conformance-tests-folder CONFORMANCE_TESTS_FOLDER
+                        Location of the folder where generated conformance test files will be written.
+  --conformance-tests-script CONFORMANCE_TESTS_SCRIPT
+                        Name of a shell script to run conformance tests. The script will receive
+                        the build folder and the conformance tests subfolder as its parameters.
   --api [API]           Force using the API (for internal use).
   --api-key API_KEY     API key used to access the API. If not provided, the CLAUDE_API_KEY
                         environment variable is used.

codeplain_REST_api.py

@@ -154,8 +154,8 @@ def refactor_source_files_if_needed(self, files_to_check, existing_files_content
         return self.post_request(endpoint_url, headers, payload)
 
 
-    def render_e2e_tests(self, frid, functional_requirement_id, plain_source_tree, linked_resources, existing_files_content):
-        endpoint_url = f"{self.api_url}/render_e2e_tests"
+    def render_conformance_tests(self, frid, functional_requirement_id, plain_source_tree, linked_resources, existing_files_content):
+        endpoint_url = f"{self.api_url}/render_conformance_tests"
         headers = {
             "X-API-Key": self.api_key,
             "Content-Type": "application/json"
@@ -187,8 +187,8 @@ def generate_folder_name_from_functional_requirement(self, functional_requiremen
         return self.post_request(endpoint_url, headers, payload)
 
 
-    def fix_e2e_tests_issue(self, frid, functional_requirement_id, plain_source_tree, linked_resources, existing_files_content, code_diff, e2e_tests_files, e2e_tests_issue, implementation_fix_count):
-        endpoint_url = f"{self.api_url}/fix_e2e_tests_issue"
+    def fix_conformance_tests_issue(self, frid, functional_requirement_id, plain_source_tree, linked_resources, existing_files_content, code_diff, conformance_tests_files, conformance_tests_issue, implementation_fix_count):
+        endpoint_url = f"{self.api_url}/fix_conformance_tests_issue"
         headers = {
             "X-API-Key": self.api_key,
             "Content-Type": "application/json"
@@ -201,8 +201,8 @@ def fix_e2e_tests_issue(self, frid, functional_requirement_id, plain_source_tree
             "linked_resources": linked_resources,
             "existing_files_content": existing_files_content,
             "code_diff": code_diff,
-            "e2e_tests_files": e2e_tests_files,
-            "e2e_tests_issue": e2e_tests_issue,
+            "conformance_tests_files": conformance_tests_files,
+            "conformance_tests_issue": conformance_tests_issue,
             "implementation_fix_count": implementation_fix_count
         }
 

examples/example_hello_world_react/hello_world_react.plain

@@ -8,7 +8,7 @@
 
 ***Test Requirements:***
 
-- End-to-end tests should be written in TypeScript, using Cypress as the end-to-end testing framework.
+- The Conformance Tests should be written in TypeScript, using Cypress as the framework for The Conformance Tests.
 
 
 ***Functional Requirements:***

examples/example_hello_world_react/run.sh

@@ -27,17 +27,17 @@ if [ $VERBOSE -eq 1 ]; then
 fi
 
 # Construct the command with optional parameters
-CMD="python ../../plain2code.py hello_world_react.plain --e2e-tests-script=../../test_scripts/run_e2e_tests_cypress.sh"
+CMD="python ../../plain2code.py hello_world_react.plain --conformance-tests-script=../../test_scripts/run_conformance_tests_cypress.sh"
 if [ $VERBOSE -eq 1 ]; then
     CMD="$CMD -v"
 fi
 if [ ! -z "$API_ENDPOINT" ]; then
     CMD="$CMD --api $API_ENDPOINT"
 fi
 
-# Removing all the end-to-end tests before rendering the hello world example.
-rm -rf e2e_tests
-rm -rf node_e2e_tests
+# Removing all the conformance tests before rendering the hello world example.
+rm -rf conformance_tests
+rm -rf node_conformance_tests
 
 # Execute the command
 $CMD
@@ -48,7 +48,7 @@ if [ $? -ne 0 ]; then
     exit 1
 fi
 
-../../test_scripts/run_e2e_tests_cypress.sh build harness_tests/hello_world_display ${VERBOSE:+-v}
+../../test_scripts/run_conformance_tests_cypress.sh build harness_tests/hello_world_display ${VERBOSE:+-v}
 
 # Check if the test harness has failed for the hello world example
 if [ $? -ne 0 ]; then