test test

testomatio · Feb 5, 2025 · 093ce08 · 093ce08
1 parent bad1e37
commit 093ce08
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/src/content/docs/getting-started/image.png b/src/content/docs/getting-started/image.png
diff --git a/src/content/docs/getting-started/index.md b/src/content/docs/getting-started/index.md
@@ -32,6 +32,8 @@ The type of your new project will influence the look of your interface, as well
 * Within a **BDD Project**, you will have feature definitions written both in the source code (by engineers) and in Testomatio (by managers and QAs). So you will be able to track and plan Cucumber automation, as well as synchronize the actual feature files with relevant test cases. When a scenario has changed in the system, but has not been updated in the code yet, you will be notified that this certain scenario is out of date.
 * Within a **Classical Project**, test cases will be written in free form using markdown. Automated tests will be synced up with test cases, so you will be able to see the test description in one tab and the corresponding test code in another tab. When a description of a test case undergoes changes, you will be notified that a certain test might need to be updated.
 
+Test test test
+
 Let's start creating a project:
 
 1. Fill the name of your project in the **Project Title** field.