137 say in $HGSRC:: |
137 say in $HGSRC:: |
138 |
138 |
139 $ cd tests |
139 $ cd tests |
140 $ python $HGSRC/tests/run-tests.py |
140 $ python $HGSRC/tests/run-tests.py |
141 |
141 |
|
142 When certain blocks of code need to cope with API changes in core Mercurial, |
|
143 they should have comments in the ``hg <= x.y (commit hash)`` format. For |
|
144 example, if a function needs another code path because of changes introduced in |
|
145 02802fa87b74 that was first included in Mercurial 5.3, then the comment should |
|
146 be:: |
|
147 |
|
148 # hg <= 5.2 (02802fa87b74) |
|
149 |
|
150 See also tests/test-check-compat-strings.t. |
|
151 |
142 Branch policy |
152 Branch policy |
143 ------------- |
153 ------------- |
144 |
154 |
145 The evolve test are highly impacted by changes in core. To deal with this, we use named branches. |
155 The evolve tests are highly impacted by changes in core. To deal with this, we |
146 |
156 use named branches. |
147 There are two main branches: "stable" and "default". Tests on these branch are |
157 |
148 supposed to pass with the corresponding "default" and "stable" branch from core |
158 There are two main branches: "stable" and "default". Tests on these branches |
149 Mercurial. The documentation is built from the tip of stable. |
159 are supposed to pass with the corresponding "default" and "stable" branch from |
150 |
160 core Mercurial. The documentation is built from the tip of stable. |
151 In addition, we have compatibility branches to check tests on older version of |
161 |
|
162 In addition, we have compatibility branches to check tests on older versions of |
152 Mercurial. They are the "mercurial-x.y" branches. They are used to apply |
163 Mercurial. They are the "mercurial-x.y" branches. They are used to apply |
153 expected test change only, no code change should happen there. |
164 expected test changes only, no code changes should happen there. |
154 |
165 |
155 test output change from a changeset in core should adds the following line to their description: |
166 Test output changes from a changeset in core should add the following line to |
|
167 their patch description: |
156 |
168 |
157 CORE-TEST-OUTPUT-UPDATE: <CORE-NODE-ID> |
169 CORE-TEST-OUTPUT-UPDATE: <CORE-NODE-ID> |
158 |
170 |
159 |
171 |
160 Format-source config |
172 Format-source config |