resolved merge conflicts

Author: FayisRahman

docs/.vitepress/config.mjs

@@ -22,9 +22,9 @@ export default defineConfig({
 		},
 
 		nav: [
-			// { text: 'Home', link: '/' },
 			{ text: 'Roadmap', link: '/roadmap/' },
 			{ text: 'Guides', link: '/guides/' },
+			{ text: 'Tests', link: '/tester/' },
 			{ text: 'About', link: '/about' },
 		],
 
@@ -230,6 +230,39 @@ export default defineConfig({
 					],
 				},
 			],
+
+			'/tester/': [
+				{
+					text: 'Installation',
+					collapsed: true,
+					items: [
+						{ text: 'Installation', link: '/tester/installation/' },
+						{ text: 'Frontend', link: '/tester/installation/frontend' },
+						{ text: 'Backend', link: '/tester/installation/backend' }
+					]
+				},
+				{
+					text: 'Tests',
+					collapsed: false,
+					items: [
+						{ text: 'Stage 1: TCP Server', link: '/tester/tests/stage1' },
+						{ text: 'Stage 3: UDP Multithreading', link: '/tester/tests/stage3' },
+						{ text: 'Stage 4: Linux Epoll', link: '/tester/tests/stage4' },
+						{ text: 'Stage 5: TCP Proxy', link: '/tester/tests/stage5' },
+						{ text: 'Stage 6: Listener & Connection Module', link: '/tester/tests/stage6' },
+						{ text: 'Stage 7: Core & Loop Module', link: '/tester/tests/stage7' },
+						{ text: 'Stage 8: Non-Blocking Sockets', link: '/tester/tests/stage8' },
+						{ text: 'Stage 9: Epoll Edge Triggering', link: '/tester/tests/stage9' },
+						{ text: 'Stage 10: Pipe Module', link: '/tester/tests/stage10' },
+						{ text: 'Stage 11: Upstream Module', link: '/tester/tests/stage11' },
+						{ text: 'Stage 12: File Module', link: '/tester/tests/stage12' },
+						{ text: 'Stage 13: Session Module', link: '/tester/tests/stage13' },
+						{ text: 'Stage 14: HTTP Request Module', link: '/tester/tests/stage14' },
+						{ text: 'Stage 15: HTTP Response Module', link: '/tester/tests/stage15' },
+						{ text: 'Stage 16: HTTP Config Module', link: '/tester/tests/stage16' },
+					],
+				},
+			],
 		},
 
 		socialLinks: [{ icon: 'github', link: 'https://github.com/eXpServer' }],

docs/assets/tester/console.png

@@ -384,6 +384,10 @@ int main() {
 
 ### Milestone #2
 
+::: tip AUTOMATED TESTS
+You can verify your implementation using the [Stage 1 Automated Tests](/tester/tests/stage1).
+:::
+
 It is time to test the server! As before, open 2 terminals, one for the TCP server that we just wrote and another for the netcat client. Start the server followed by the client.
 
 Upon the successful connection of the client to the server, the server terminal should display:

docs/assets/tester/execute.png

@@ -314,6 +314,9 @@ int main() {
     return 0;
 }
 ```
+::: tip AUTOMATED TESTS
+You can verify your implementation using the [Stage 3 Automated Tests](/tester/tests/stage3).
+:::
 
 ## Conclusion
 

docs/assets/tester/failed.png

@@ -297,6 +297,10 @@ Here is the expected output:
 
 ![milestone-2.png](/assets/stage-3/milestone-2.png)
 
+::: tip AUTOMATED TESTS
+You can verify your implementation using the [Stage 4 Automated Tests](/tester/tests/stage4).
+:::
+
 ## Conclusion
 
 The server is now capable of handling multiple clients simultaneously using the _epoll_ I/O event notification mechanism in Linux. Recall that this is one of the methods that can be done to provide concurrency.

docs/assets/tester/intro_1.png

@@ -384,6 +384,10 @@ The proxy should go back to the `epoll_wait` state and wait for more events.
 
 Keep testing the code by navigating across the file server, and opening files. Make sure the proxy does not exit out of the program.
 
+::: tip AUTOMATED TESTS
+You can verify your implementation using the [Stage 5 Automated Tests](/tester/tests/stage5).
+:::
+
 ## Experiments
 
 ### Experiments #1