Skip to content

Commit f0d4fb4

Browse files
authored
Updated introduction
Added introduction and made minor text fixes
1 parent 016a619 commit f0d4fb4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/ContinuousIntegration.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,11 @@
1717

1818
## Introduction
1919

20-
FIXME: FILL ME IN!
20+
This page is designed to assist in the understanding of proper practices for testing for the Swift project.
2121

2222
## Pull Request Testing
2323

24-
In order for the Swift project to be able to advance quickly, it is important that we maintain a green build [[1]](#footnote-1). In order to help maintain this green build, the Swift project heavily uses pull request (PR) testing. Specifically, an important general rule is that **all** non-trivial checkins to any Swift Project repository should should at least perform a [smoke test](#smoke-testing) if simulators will not be impacted *or* a full [validation test](#validation-testing) if simulators may be impacted. If in addition one is attempting to make a source breaking change across multiple repositories one should follow the cross repo source breaking changes workflow. We now continue by describing the Swift system for Pull Request testing, @swift-ci:
24+
In order for the Swift project to be able to advance quickly, it is important that we maintain a green build [[1]](#footnote-1). In order to help maintain this green build, the Swift project heavily uses pull request (PR) testing. Specifically, an important general rule is that **all** non-trivial checkins to any Swift Project repository should at least perform a [smoke test](#smoke-testing) if simulators will not be impacted *or* a full [validation test](#validation-testing) if simulators may be impacted. If in addition one is attempting to make a source breaking change across multiple repositories, one should follow the cross repo source breaking changes workflow. We now continue by describing the Swift system for Pull Request testing, @swift-ci:
2525

2626
### @swift-ci
2727

@@ -102,7 +102,7 @@ With that being said, a validation test on macOS does the following:
102102
1. Removes the workspace.
103103
2. Builds the compiler.
104104
3. Builds the standard library for macOS and the simulators for all platforms.
105-
4. lldb is /not/ build/tested [[2]](#footnote-2)
105+
4. lldb is /not/ built/tested [[2]](#footnote-2)
106106
5. The tests, validation-tests are run for all simulators and macOS both with
107107
and without optimizations enabled.
108108

0 commit comments

Comments
 (0)