Skip to content

Support partitioning at the scenario level instead of feature file level #104

Description

@GoogleCodeExporter
Hi

Right now, I TLB considers a feature file as the smallest unit. In other words, 
if we have one feature file with 10 scenario and if we have 2 partitions, this 
feature file will be passed to one balancer and other will be idle.
Another example is , if we have two feature file , one with 15 scenarios and 
other with 2, we will see a little benefit from TLB unless both feature file 
takes almost the same time.

Is there any plan to add a feature where individual scenarios can be passed to 
balancers instead of feature files ?

This is neither a big problem right now nor a blocking issue, but i think a 
nice to have feature. I can see this will have performance impact on TLB 
because of parsing the feature file, scenarios which relies on background 
keyword,etc.

Regards
Ragavan

Original issue reported on code.google.com by singh.janmejay on 30 Jun 2012 at 6:15

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions