Add Docker Authentication Testing and Results documentation

README.md

@@ -22,12 +22,38 @@ The following setup was implemented on the kistembd VM for GitLab runners:
 
 * A runner was configured with a group token for mbd_outreach.
 
-* Pipelines were triggered for presentation-platform and presentation-platform-1.
+* Pipelines were triggered for mbd_outreach/presentation-platform and mbd_outreach/presentation-platform-1.
 
-**Result:** ✅ Passed. Both repositories successfully pushed and pulled images using the same runner and token.
+**Result:** ✅ Passed. 
+
+* Push and pull operations work seamlessly.
+
+* New images can be pushed to other repositories in the same group.
+
+* Each repository can use images from others within the same group.
 
 **Test Case 2: Cross-Group Authentication**
 
+**Objective:** Verify that authentication works independently across different GitLab groups without conflicts.
+
+**Setup:**
+
+* A runner was configured for mbd_outreach/presentation-platform.
+
+* Another runner was configured for gitlab-credential-test/presentation.
+
+* Pipelines were triggered for both repositories.
+
+**Result:** ✅ Passed
+
+* Tested with mbd_outreach/presentation-platform and gitlab-credential-test/presentation.
+
+* Push and pull operations work without affecting each other.
+
+* No authentication conflicts occurred between the groups.
+
+**Test Case 3: Unauthorized Cross-Group Authentication**
+
 **Objective:** Test authentication failure when using a token from Group 1 in a runner for Group 2.
 
 **Setup:**
@@ -42,48 +68,64 @@ The following setup was implemented on the kistembd VM for GitLab runners:
 
 **Result:** ❌ Failed. Authentication failed as expected since a token from mbd_outreach cannot authenticate in gitlab_credential_test.
 
-**Test Case 3: Subgroup Authentication Hierarchy**
+**Test Case 4 : Subgroup Authentication Hierarchy**
 
-**Objective:** Validate the inheritance and limitations of authentication tokens across subgroups.
+**Objective:** Verify how authentication tokens are inherited and used across subgroups within a GitLab group.
 
 **Setup:**
 
-* Group 1: mbd_outreach
+* Parent Group: mbd_outreach
 
-* Subgroup 1: outreach_1 (Runner configured with token_outreach_1)
+* Subgroup 1: outreach_1 (Has a dedicated runner configured with token_outreach_1)
 
-* Subgroup 2: outreach_2 (Runner only inherits the group runner if active)
+* Subgroup 2: outreach_2 (Does not have its own runner but can inherit the group's runner if active)
 
 **Results:**
 
-✅ outreach_1 pipelines always succeeded.
+✅ outreach_1 pipelines always succeed because it has a dedicated runner with a valid token.
 
-✅ outreach_2 pipelines succeeded only when the group runner for mbd_outreach was active.
+✅ outreach_2 pipelines succeed only if the mbd_outreach group runner is active since it relies on inheritance.
 
-❌ If no active runner was present in mbd_outreach, outreach_2 pipeline failed.
+❌ outreach_2 pipelines fail if the mbd_outreach group runner is inactive, as there is no available runner for authentication.
 
-**Test Case 4: Shared Runner Authentication**
+**Test Case 5: Shared Runner Authentication**
 
-**Objective:** Verify if two subgroups using the same runner and token can execute pipelines successfully.
+**Objective:**Verify that multiple subgroups can successfully execute pipelines using a shared runner inherited from the parent group.
 
 **Setup:**
 
-Both outreach_1 and outreach_2 inherited Runner 1, which was registered with token_outreach_1.
+* Parent Group: mbd_outreach (Has an active runner)
+
+* Subgroup 1: outreach_1 (Inherits the runner from mbd_outreach)
+
+* Subgroup 2: outreach_2 (Inherits the runner from mbd_outreach)
 
-**Result:** ✅ Passed. Both subgroups successfully executed pipelines using the shared runner and token.
+**Result:** ✅ Passed. 
+Both outreach_1 and outreach_2 successfully executed pipelines using the shared runner from mbd_outreach.
 
-**Test Case 5: Multi-GitLab Instance Authentication**
+**Test Case 6: Multi-GitLab Instance Authentication**
 
-**Objective:** Ensure runners on the same VM can authenticate to separate GitLab instances simultaneously.
+**Objective:** Verify that runners on the same VM can authenticate and execute pipelines for separate GitLab instances without conflicts.
 
 **Setup:**
 
-* Two GitLab instances: git and git-ce
+**GitLab Instance 1 (git)**
+
+* Group: gitlab-credential-test
+
+* Runner: Runner1 (Configured with Group 1 credentials)
+
+* Repository: presentation
+
+**GitLab Instance 2 (git-ce)**
+
+* Group: gitlab-credential-ce
 
-* Group 1 (git): gitlab-credential-test, Runner1 with Group1 credentials
+* Runner: Runner2 (Configured with Group 2 credentials)
 
-* Group 2 (git-ce): gitlab-credential-ce, Runner2 with Group2 credentials
+* Repository: presentation-ce
 
-* Pipelines triggered simultaneously in presentation (Repo1) and presentation-ce (Repo2)
+- Pipelines were triggered simultaneously in presentation (Instance git) and presentation-ce (Instance git-ce).
 
-**Result**:✅Passed. Both pipelines executed successfully without authentication conflicts.
\ No newline at end of file
+**Result**:✅Passed.
+ Both pipelines executed successfully without authentication conflicts.
\ No newline at end of file