Skip to content

Commit 578d37b

Browse files
DavertMikDavertMik
committed
added badges for 4.x docs
1 parent d685907 commit 578d37b

15 files changed

+33
-2
lines changed

‎docs/4.x/APITesting.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: APITesting - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/APITesting">Read for latest version</a></div>
7+
68
# API Testing
79

810
The same way we tested a web site, Codeception allows you to test web services. They are very hard to test manually, so it's a really good idea to automate web service testing. We have SOAP and REST as standards, which are represented in corresponding modules, which we will cover in this chapter.

‎docs/4.x/AcceptanceTests.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,9 @@ layout: doc
33
title: AcceptanceTests - Codeception 4 Documentation
44
---
55

6+
7+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/AcceptanceTests">Read for latest version</a></div>
8+
69
# Acceptance Testing
710

811
Acceptance testing can be performed by a non-technical person. That person can be your tester, manager or even client.

‎docs/4.x/AdvancedUsage.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: AdvancedUsage - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/AdvancedUsage">Read for latest version</a></div>
7+
68
# Advanced Usage
79

810
In this chapter we will cover some techniques and options that you can use to improve your testing experience

‎docs/4.x/BDD.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: BDD - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/BDD">Read for latest version</a></div>
7+
68
# Behavior Driven Development
79

810
Behavior Driven Development (BDD) is a popular software development methodology. BDD is considered an extension of TDD, and is greatly inspired by [Agile](https://agilemanifesto.org/) practices. The primary reason to choose BDD as your development process is to break down communication barriers between business and technical teams. BDD encourages the use of automated testing to verify all documented features of a project from the very beginning. This is why it is common to talk about BDD in the context of test frameworks (like Codeception). The BDD approach, however, is about much more than testing - it is a common language for all team members to use during the development process.
@@ -644,4 +646,4 @@ If you like the concept of Behavior Driven Development or prefer to keep test sc
644646
* **Next Chapter: [Customization >](/docs/08-Customization)**
645647
* **Previous Chapter: [< AdvancedUsage](/docs/07-AdvancedUsage)**
646648

647-
<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/4.x/BDD.md"><strong>Edit</strong> this page on GitHub</a></div>
649+
<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/4.x/BDD.md"><strong>Edit</strong> this page on GitHub</a></div>

‎docs/4.x/Codecoverage.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: Codecoverage - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/Codecoverage">Read for latest version</a></div>
7+
68
# Code Coverage
79

810
At some point you want to review which parts of your application are tested well and which are not.

‎docs/4.x/ContinuousIntegration.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: ContinuousIntegration - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/ContinuousIntegration">Read for latest version</a></div>
7+
68
# Continuous Integration
79

810
Once you get testing suite up and running you are interested in running your tests regularly. If you ensure that tests are running on every code change or at least once a day you can be sure that no regression is introduced. This allows to keep you system stable. But developers are not so passionate about running all tests manually, they also can forget to execute tests before pushing code to production... The solution is simple, test execution should be automated. Instead of running them locally it is better to have dedicated server responsible for running tests for a team. This way we can ensure that everyone's tests executed, which commit made a regression in codebase, and that we can deploy only once tests pass.

‎docs/4.x/Customization.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: Customization - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/Customization">Read for latest version</a></div>
7+
68
# Customization
79

810
In this chapter we will explain how you can extend and customize the file structure and test execution routines.

‎docs/4.x/Data.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: Data - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/Data">Read for latest version</a></div>
7+
68
# Working with Data
79

810
Tests should not affect each other. That's a rule of thumb. When tests interact with a database,

‎docs/4.x/FunctionalTests.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: FunctionalTests - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/FunctionalTests">Read for latest version</a></div>
7+
68
# Functional Tests
79

810
Now that we've written some acceptance tests, functional tests are almost the same, with one major difference:

‎docs/4.x/GettingStarted.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ layout: doc
33
title: GettingStarted - Codeception 4 Documentation
44
---
55

6+
<div class="alert alert-warning">👴 <b>You are reading docs for Codeception 4</b>. Current version is 5.x <a href="/docs/GettingStarted">Read for latest version</a></div>
7+
68
# Getting Started
79

810
Let's take a look at Codeception's architecture. We'll assume that you have already [installed](https://codeception.com/install) it

0 commit comments

Comments
 (0)