Testing guidelines

doctrine · Oct 18, 2020 · 4c5b4a0 · 4c5b4a0
1 parent 5f4b6fe
commit 4c5b4a0
Showing 1 changed file with 32 additions and 0 deletions.
diff --git a/docs/en/reference/testing.rst b/docs/en/reference/testing.rst
@@ -0,0 +1,32 @@
+Testing Guidelines
+===================
+
+Some intro.
+
+Purpose
+-------
+
+1. Help maintainers understand what problem the given code change is trying to solve.
+2. Make sure that the problem being solved needs to be solved in the DBAL.
+3. Prevent breakages of the logic by new code changes.
+
+Requirements
+------------
+
+Each pull request that adds new or changes the existing logic must have tests.
+
+Unit Tests
+----------
+
+Integration Tests
+-----------------
+
+Integration (a.k.a. functional) test are required when the behavior under the test is dictated by the logic
+defined outside of the DBAL. It could be:
+
+1. The underlying database platform.
+2. The underlying database driver.
+3. SQL syntax and the standard as such.
+
+TODO:
+Why it's important to cover the above with integration tests?