Page History

...

Each .feature file will be processed as follows.and will try to find or create a Test/Pre-Condition inside the project given in the projectKey parameter. We use the following rules:

Tests:

1. try to find the Test by key (in that project), if found then update it; else...
2. try to find the Test having both:
   1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
   2. a label named "id:xxx", where xxx is some number (e.g. "id:1", "id:32"); this label comes from a scenario/scenario outline's tag
   3. no other label ending in ".feature"
3. try to find the Test having both:
   
   1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
   2. the same summary
   3. no other label ending in ".feature"
4. try to find the Test by summary (in that project), if found then update it; else...having:
   1. the same Summary
   2. no label ending in ".feature", except the one corresponding to the relative path of the Cucumber file being imported
5. create Test in that project and add a label with the relative path of the feature, and another label corresponding to a tag "id:xxx" (if it exists). The tags used in the scenario/scenario outline are also added as labels.

Pre-Conditions:

1. try to find the Pre-Condition by key (in that project), if found then update it; else...
2. try to find the Pre-Condition having both:
   1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
   2. no other label ending in ".feature"
3. try to find the Pre-Condition by summary (in that project), if found then update it; else...the Pre-Condition having both:
   1. the same Summary
   2. no label ending in ".feature", except the one corresponding to the relative path of the Cucumber file being imported
4. create Pre-Condition in that project and add a label with the relative path of the feature

...