https://issues.apache.org/bugzilla/show_bug.cgi?id=50475
Summary: Introduction of a Test Fragment Test Element for a
better Include flow
Product: JMeter
Version: 2.3.4
Platform: Macintosh
Status: NEW
Severity: enhancement
Priority: P2
Component: Main
AssignedTo: [email protected]
ReportedBy: [email protected]
Created an attachment (id=26403)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=26403)
testFragment Patch of MenuFactory, TestPlan and IncludeController to support
this enhancement
The Include and Module controller logic currently has some bad user flows.
Here is the main one I see:
User Flow: Update Include File
1. Open Existing Include File
-- Contained Element is automatically added to WorkBench
2. Edit File
3. Click on desired Node
4. File->Save Selection As
5. Rename file if needed(it takes the name of the Node()
6. Overwrite Existing? -> Yes
This overly complicated flow is introduced because Include-type JMX files are
second-rate citizens. They are not part of a Test Plan so they cannot be
automatically saved with Ctrl+S. Also, since they cannot contain any save-able
Thread Groups, they have to be debugged with another Test Plan that imports it.
This is another bad user-flow.
Enhancement: Introduce a sub-TestPlan Test Element named Test Fragment that
can be used for holding non-executing trees.
This element behaves like the Thread Group except that it doesn't execute
during a Run->Start. Since it exists underneath the Test Plan element, it can
be saved in the more natural flow preventing users from accidentally
over-writing their include file with a blank Test Plan. The IncludeController
would be enhanced to support importing these Test Fragments while maintaining
support for the non-Test Plan JMX files that already exist.
A side-affect of this change is that a user could also create a Thread Group
for the Include File that can Regress the Test Fragment logic by simply using
the ModuleController to run the Test Fragment Tree.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
