esnme/locust — Issue #16: Remove SubLocust and merge into Locust class
Author: cgbystrom
Created: 2012-01-10 23:52:45+00:00
State: open
Labels: proposal

Looking at a normal Locust script I find SubLocusts confusing since they seem to differ so little from a normal Locust class.

As I haven't been involved with SubLocusts, what was the original idea of creating a separate class for it? Looking at code it should be fairly simple to merge it into Locust class. Would simplify the API for end-users.

Also, using Locust classes both for user representation and essentially task grouping/task sets creates a bit of complexity.
Perhaps just one of them, either the user representation or task group need a new name better explaining it's purpose?
That would avoid some confusion of the two.