Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Developer Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
brienne
Developer Documentation
Commits
59dd5b76
Commit
59dd5b76
authored
7 years ago
by
totten
Browse files
Options
Downloads
Patches
Plain Diff
testing/index.md - Use fewer words
parent
986bdef6
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/testing/index.md
+3
-4
3 additions, 4 deletions
docs/testing/index.md
with
3 additions
and
4 deletions
docs/testing/index.md
+
3
−
4
View file @
59dd5b76
...
...
@@ -149,10 +149,9 @@ possible inputs/permutations.
### Headless test {:#headless}
The most common kind of automated test in
`civicrm-core`
is a
**headless test**
. A headless test focuses on a combination of artifacts, such as
multiple PHP classes and a database. Headless tests have a
*nearly complete*
CiviCRM environment, but some elements (such as the web server and CMS)
are omitted. This is ideally suited to testing data-management APIs (where the DBMS is an important part of the system) and other portable services
(where you wouldn't expect the CMS or HTTPD to influence behavior).
The most common kind of automated test in
`civicrm-core`
is a
**headless test**
. Headless tests use a
*nearly complete*
CiviCRM environment;
however, there is no CMS or web-server, and all data is stored on a private, headless database. This is ideally suited to testing data-management
APIs (where the DBMS is an important part of the system) and other portable services (where you wouldn't expect the CMS to influence behavior).
!!! tip "Headless tests and safety"
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment