Test frameworks update for support to test projects

demonstrators-line/demonstrator-v0/pom.xml

@@ -2,7 +2,7 @@
 	<modelVersion>4.0.0</modelVersion>
 	<groupId>org.cybnity</groupId>
 	<artifactId>techstack</artifactId>
-	<version>0.46.0</version>
+	<version>0.47.0</version>
 	<packaging>pom</packaging>
 	<name>CYBNITY Official Standard Techstack</name>
 
@@ -59,7 +59,8 @@
 		<janusgraph.inmemory>1.1.1-20250608-090326.0289ebc</janusgraph.inmemory>
 		<junit-jupiter.version>5.9.3</junit-jupiter.version> <!-- 5.7.0 -->
 		<junit-jupiter-platform.version>[1.9.2,)</junit-jupiter-platform.version>
-		<cucumber.version>7.12.1</cucumber.version>
+		<testng.version>7.9.0</testng.version> <!-- For 7.9.0 JDK-11; else 7.5.1 for JDK-8 -->
+		<cucumber.version>7.34.3</cucumber.version> <!-- original version was 7.12.1-->
 
 		<!-- Docker base images reusable by CYBNITY containerized modules -->
 
@@ -163,7 +164,15 @@
 				<version>4.2.12.Final</version>
 				<scope>compile</scope>
 			</dependency>
+			<dependency>
+				<!-- TestNG test plans management tool -->
+				<groupId>org.testng</groupId>
+				<artifactId>testng</artifactId>
+				<version>${testng.version}</version>
+				<scope>test</scope>
+			</dependency>
             <dependency>
+				<!-- Behaviour-Drivcen Development Test framework -->
                 <groupId>io.cucumber</groupId>
                 <artifactId>cucumber-bom</artifactId>
                 <version>${cucumber.version}</version>

demonstrators-line/demonstrator-v0/sample-project-pom.xml

@@ -3,7 +3,7 @@
 	<parent>
 		<groupId>org.cybnity</groupId>
 		<artifactId>techstack</artifactId>
-		<version>0.46.0</version>
+		<version>0.47.0</version>
 	</parent>
 
 	<groupId>org.cybnity.techstack.quality</groupId>

demonstrators-line/demonstrator-v0/technologies-stack-analysis.md

@@ -180,6 +180,8 @@ The current status of technology already in the analysis stream give a general v
 | OPERATING TOOLS | Kubernetes Cluster Monitoring | [Kubernetes Dashboard](https://sysdig.com/learn-cloud-native/kubernetes-101/what-is-the-kubernetes-dashboard/) | `WIN` | | | web-based UI to perform basic operating tasks and review Kubernetes cluster events |
 | BUILD TOOL | Component Features Specification & Automated Testing | [Concordion](https://concordion.org/tutorial/java/markdown/) | `WIN` | | | Creation of living documentation (documenting, instrumenting, coding) regarding software features via a Behavior-Driven Design approach (specification of features and behavior scenario via markdown in files, instrumentation/automation of test case via Java fixture codes, and tests execution under JUnit via gradlew and/or IDE) allowing features development/maintenance through Test-Driven Design practices for system components features (e.g processes, feature unit test, integration test) |
 | BUILD TOOL | UI Features Automated Testing | [Cypress](https://www.cypress.io/features) | `WIN` | | | All-in-one testing framework, assertion library, with mocking and stubbing, all without Selenium installation. End-to-end testing of web UI features |
+| BUILD TOOL | Behavior-Driven Development | [Cucumber](https://cucumber.io/docs) | `WIN` | `WIN` | `WIN` | Cucumber reads executable specifications written in plain text and validates that the software does what those specifications say. The specifications consist of multiple examples, or scenarios constituing UAT or integration automated tests |
+| BUILD TOOL | Application Test Management | [TestNG](https://testng.org/) | `WIN` | `WIN` | `WIN` | Application tests management tool allowing large test plans grouping, execution, enhanced reports and integration with Cucumber test tool |
 | BUILD TOOL | Components Builder | [Maven](https://maven.apache.org/) | `WIN` | `WIN` | `WIN` | Build binaries (e.g application components) from VCS, install into local repository, and deploy to Artifacts Repository |
 | BUILD TOOL | Infrastructure-As-Code (IaC) | [Terraform](https://www.terraform.io/) | `WIN` | `ALT` | `X` | Provisioning management of networking, load balancer, database, users, permissions... and Kubernetes cluster (orchestration management); integration via providers (e.g OVH Cloud), with Docker (server templating) and Helm (configuration management as repeatable application installer), with Argo CD (assembly and installation management) |
 | BUILD TOOL | Infrastructure-As-Code (IaC) | [Opentofu](https://github.com/opentofu/opentofu) | `WIN` | `WIN` | `X` | Provisioning management of networking, load balancer, database, users, permissions... based on Terraform (fork); integration via providers, with Docker (server templating) and Helm (configuration management as repeatable application installer). Fork of Terraform project who changed the license model |

demonstrators-line/demonstrator-v0/v0-technologies-stack.md

@@ -68,8 +68,8 @@ Should allow definition and test of basic software factory implementation allowi
 None supervision requirements required regarding the step of the CYBNITY Foundation project.
 
 # CURRENT MPP OFFICIAL VERSION
-- Version: 0.46.0
-- Released at: April, 23, 2026
+- Version: 0.47.0
+- Released at: May 22, 2026
 - Status: `RELEASED`
 - Documentation: [technologies-stack-analysis](technologies-stack-analysis.md)
 - Deliverables:
@@ -80,7 +80,7 @@ None supervision requirements required regarding the step of the CYBNITY Foundat
     <parent>
       <groupId>org.cybnity</groupId>
       <artifactId>techstack</artifactId>
-      <version>0.46.0</version>
+      <version>0.47.0</version>
     </parent>
 
     <repositories>