Confirmed users
1,905
edits
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
The test files used by CrossWeave are all written in JSON; these drive the test. There is no scripting required to create test cases. | The test files used by CrossWeave are all written in JSON; these drive the test. There is no scripting required to create test cases. | ||
The general format of a CrossWeave test is as follows | The general format of a CrossWeave test is as follows: | ||
setup | setup | ||
profiles: profile- | profiles: [profile1, profile2, ..., profile-n] | ||
asset-list-1 | asset-list-1 | ||
... | ... | ||
asset-list-n | asset-list-n | ||
phase-1 | phase-1: | ||
profile | profile: profile1 | ||
actions | actions: [action1, action2, ..., action-n] | ||
phase-2 | phase-2: | ||
profile | profile: profile2 | ||
actions | actions: [action1, action2, ..., action-n] | ||
... | ... | ||
phase-n | phase-n: | ||
profile | profile: profile1 | ||
actions | actions: [action1, action2, ..., action-n] | ||
== The Setup Block == | |||
The setup block just lists the profiles that will be used during the test. CrossWeave creates these profiles before Firefox is launched. The profiles can be given any names. A complete setup block might look like: | |||
"setup": { | |||
"profiles": ["profile1", "profile2", "profileHailMary"] | |||
}, |