Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 <?xml version="1.0" encoding="UTF-8"?> | 1 <?xml version="1.0" encoding="UTF-8"?> |
| 2 <!-- ====================================================================== | 2 <!-- ====================================================================== |
| 3 Sep 6, 2011 4:04:51 PM | 3 Sep 6, 2011 4:04:51 PM |
| 4 | 4 |
| 5 Dart Tools Tests Build | 5 Dart Tools Tests Build |
| 6 Build the Dart Tools tests and then run them over the Dart code | 6 Build the Dart Tools tests and then run them over the Dart code |
| 7 | 7 |
| 8 Mark R Russell (mrrussell@google.com) | 8 Mark R Russell (mrrussell@google.com) |
| 9 ====================================================================== --> | 9 ====================================================================== --> |
| 10 <project name="Dart Tools Tests Build" default="test"> | 10 <project name="Dart Tools Tests Build" default="test"> |
| (...skipping 155 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 166 </parallel> | 166 </parallel> |
| 167 <mkdir dir="${build.test.reports.dir}" /> | 167 <mkdir dir="${build.test.reports.dir}" /> |
| 168 <move todir="${build.test.reports.dir}"> | 168 <move todir="${build.test.reports.dir}"> |
| 169 <fileset dir="."> | 169 <fileset dir="."> |
| 170 <include name="**/TEST-*.xml" /> | 170 <include name="**/TEST-*.xml" /> |
| 171 </fileset> | 171 </fileset> |
| 172 </move> | 172 </move> |
| 173 </target> | 173 </target> |
| 174 | 174 |
| 175 <!-- We have not set "failonerror='true'" for either the test runner | 175 <!-- We have not set "failonerror='true'" for either the test runner |
| 176 or test collector, because we want the HTML report to be generated | 176 or test collector, because we want the HTML report to be generated |
|
danrubel
2012/12/19 14:55:32
Are we still generating an HTML report? Or should
devoncarew
2012/12/19 17:35:13
I did not change the failonerror flag. This commen
| |
| 177 even when the tests fail. Unfortunately, this will cause ant to | 177 even when the tests fail. Unfortunately, this will cause ant to |
| 178 report "BUILD SUCCESSFUL, even if the tests fail. To get around this | 178 report "BUILD SUCCESSFUL, even if the tests fail. To get around this |
| 179 problem, the -check_results task will parse the generated XML report | 179 problem, the -check_results task will parse the generated XML report |
| 180 and look for the substrings 'failures="0"' and 'errors="0"'. If either | 180 and look for the substrings 'failures="0"' and 'errors="0"'. If either |
| 181 of these strings cannot be found, then a <fail> task is run.--> | 181 of these strings cannot be found, then a <fail> task is run.--> |
| 182 <target name="check_results" depends="generateHtml"> | 182 <target name="check_results"> |
| 183 <copy | |
| 184 file="${build.test.reports.dir}/TEST-${build.test.suite}.xml" | |
| 185 tofile="${build.out}/test-results.xml"/> | |
| 183 | 186 |
| 184 <loadfile | 187 <loadfile |
| 185 srcfile="${build.test.reports.dir}/TEST-${build.test.suite}.xml" | 188 srcfile="${build.test.reports.dir}/TEST-${build.test.suite}.xml" |
| 186 property="build.results.summary"> | 189 property="build.results.summary"> |
| 187 <filterchain> | 190 <filterchain> |
| 188 <headfilter lines="10" /> | 191 <headfilter lines="10" /> |
| 189 </filterchain> | 192 </filterchain> |
| 190 </loadfile> | 193 </loadfile> |
| 191 | 194 |
| 192 <!-- TODO: This condition assumes that there is a single report file wit h a | 195 <!-- TODO: This condition assumes that there is a single report file wit h a |
| (...skipping 15 matching lines...) Expand all Loading... | |
| 208 <fail | 211 <fail |
| 209 message="FAILED - some tests failed - see the XML report in ${build. test.reports.dir} for more details" | 212 message="FAILED - some tests failed - see the XML report in ${build. test.reports.dir} for more details" |
| 210 unless="tests.passed" /> | 213 unless="tests.passed" /> |
| 211 <echo | 214 <echo |
| 212 message="SUCCESS - all tests passed - see the XML report in ${build. test.reports.dir} for more details" /> | 215 message="SUCCESS - all tests passed - see the XML report in ${build. test.reports.dir} for more details" /> |
| 213 </target> | 216 </target> |
| 214 | 217 |
| 215 <!-- | 218 <!-- |
| 216 create an HTML version of the Junit output | 219 create an HTML version of the Junit output |
| 217 --> | 220 --> |
| 218 <target name="generateHtml"> | 221 <target name="generateHtml"> |
|
danrubel
2012/12/19 14:55:32
No longer called? Remove?
devoncarew
2012/12/19 17:35:13
sgtm
| |
| 219 <junitreport> | 222 <junitreport> |
| 220 <fileset dir="${build.test.reports.dir}"> | 223 <fileset dir="${build.test.reports.dir}"> |
| 221 <include name="TEST-${build.test.suite}.xml" /> | 224 <include name="TEST-${build.test.suite}.xml" /> |
| 222 </fileset> | 225 </fileset> |
| 223 <report todir="${build.out}/html" > | 226 <report todir="${build.out}/html" > |
| 224 </report> | 227 </report> |
| 225 </junitreport> | 228 </junitreport> |
| 226 </target> | 229 </target> |
| 227 | 230 |
| 228 <!-- | 231 <!-- |
| (...skipping 211 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 440 | 443 |
| 441 <mkdir dir="${build.runtime}" /> | 444 <mkdir dir="${build.runtime}" /> |
| 442 <mkdir dir="${build.target}" /> | 445 <mkdir dir="${build.target}" /> |
| 443 <mkdir dir="${build.stage.plugins}" /> | 446 <mkdir dir="${build.stage.plugins}" /> |
| 444 <mkdir dir="${build.stage.features}" /> | 447 <mkdir dir="${build.stage.features}" /> |
| 445 <mkdir dir="${build.out}" /> | 448 <mkdir dir="${build.out}" /> |
| 446 | 449 |
| 447 </target> | 450 </target> |
| 448 | 451 |
| 449 </project> | 452 </project> |
| OLD | NEW |