Changes between Initial Version and Version 2 of Ticket #4218
- Timestamp:
- Aug 7, 2009, 5:51:53 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4218
-
Property
Status
changed from
newtoassigned - Property Owner set to Garry Yao
-
Property
Status
changed from
-
Ticket #4218 – Description
initial v2 40 40 return 41 41 { 42 variables : [ [ 'ckeditorRoot', 'path-to-CKEditor-root'] ], 42 variables : [ [ 'ckeditorRoot', 'path-to-CKEditor-root'] ], 43 43 cells : [ 44 [ 'tt/unit/htmldataprocessor/1' , []], // Implicit tags declaration by file path.44 [ 'tt/unit/htmldataprocessor/1' ], // Implicit tags declaration by file path. 45 45 [ 'ckeditor/3210.html' , [ 'ticket', 'unit', 'htmldataprocessor'] ] // Explicit tag declaration. 46 ] 46 ] 47 47 }; 48 48 } 49 49 }}} 50 50 The '''tag''' plays an important role as an identifier to denote the following aspects of a test cell: 51 1. Dependencies of the cell, e.g. if it has tags 'unit', 'ckeditor' and 'domiterator', it denote it's a unit test running by YUITest, the testing stage is CKEditor, and the domiterator pluginis required to run the test.52 2. Tagging of the cell, whether the cell should be executed when it's been run in a runner with a specific criteria. E.g. A url criteria as 'http://t/?tt&plugins' will run only the ticket test of plugins ( with 'ticket' and 'plugins' tags).51 1. Environments of the cell, e.g. if it has tags 'unit' and 'editor', it denote a unit test running by YUITest, along with the CKEditor testing stage is required to run the test. 52 2. Categories of the cell, when it's been run in a runner with a specific criteria. E.g. A url criteria as 'http://t/runner?cells=tt,plugins' will run only the ticket test of plugins ( with 'ticket' and 'plugins' tags ). 53 53 54 54 … … 64 64 to only execute the satisfied ones. 65 65 66 Before runner execute each test cell, an extensible ''' dependencyresolver''' is running there to determinate the required/requested66 Before runner execute each test cell, an extensible '''environment resolver''' is running there to determinate the required/requested 67 67 resources of a specific cell by analysing the '''tags''', guarantee the cell always has all the dependencies 68 68 it should receive. These resources are typically … … 70 70 * The testing target 71 71 * The testing library 72 * Any resources dedicate the one kind of test 72 73 73 74 === Testing Request === 74 A request is simply a loading of the runner page, it's the beginning of the testing life cycle. 75 The request could optionally consist of a criteria which is a list of tags to filter down the test cells to run, could be 75 A request is simply a loading of the runner page, which is the beginning of the testing life cycle. 76 1. The request must contains a profile param in the url to specify the location of profile of this running. 77 1. The request could optionally consist of a criteria which is a list of '''tags''' or '''path''' to filter down the test cells to run, could be 76 78 specified via : 77 79 * A ampersand separated url params; 78 80 * A predefined JSON file denote the criteria; 79 81 * Specified through UI of the test runner page; 82 Some example testing requests look like: 83 * Running only the tickets test of unit test : http://t/runner.html?profile=../profile.js&cells=tt,unit 84 * Running a specific test : http://t/runner.html?profile=../profile.js&cells=../editor/tt/unit/htmldataprocessor/1 85 * Running two specific tests : http://t/runner.html?profile=../profile.js&cells=../editor/tt/unit/htmldataprocessor/1,../editor/dd/selenium/visual/1 86
