diff --git a/docs/images/12-loadtest.png b/docs/images/12-loadtest.png
new file mode 100644
index 00000000..b6119a2e
Binary files /dev/null and b/docs/images/12-loadtest.png differ
diff --git a/docs/index.adoc b/docs/index.adoc
index 38006e65..88904767 100644
--- a/docs/index.adoc
+++ b/docs/index.adoc
@@ -93,7 +93,11 @@ include::src/10_quality_requirements.adoc[]
 include::src/11_technical_risks.adoc[]
 
 <<<<
-// 12. Glossary
-include::src/12_glossary.adoc[]
+// 12. Testing
+include::src/12_testing.adoc[]
+
+<<<<
+// 13. Glossary
+include::src/13_glossary.adoc[]
 
 
diff --git a/docs/src/12_testing.adoc b/docs/src/12_testing.adoc
new file mode 100644
index 00000000..b3a9e977
--- /dev/null
+++ b/docs/src/12_testing.adoc
@@ -0,0 +1,12 @@
+ifndef::imagesdir[:imagesdir: ../images]
+
+== Testing 
+
+This section details the results of the various types of tests that have been carried out with the application.
+
+=== Load Testing
+We used Gatling to perform load testing on the application. It consisted of simulating 1000 users accessing the application at the same time, each of one performing 83 requests. The results of the test are shown below:
+
+image::12-loadtest.png[]
+
+As we can see in Gatling's report, the application was able to handle a load of 70868 requests without any problems. In particular, 81% of the requests were successful in less than 800 milliseconds, 6% in more than 1200 milliseconds and 13% were unsuccessful. 
\ No newline at end of file
diff --git a/docs/src/12_glossary.adoc b/docs/src/13_glossary.adoc
similarity index 100%
rename from docs/src/12_glossary.adoc
rename to docs/src/13_glossary.adoc
diff --git a/gatling/gatling.md b/gatling/gatling.md
deleted file mode 100644
index 9b8e252f..00000000
--- a/gatling/gatling.md
+++ /dev/null
@@ -1,2 +0,0 @@
-# Tests de carga con Gatling
-