You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2002/05/04 02:59:15 UTC

DO NOT REPLY [Bug 8801] New: - Prompt to save Test Plan on exit

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8801>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8801

Prompt to save Test Plan on exit

           Summary: Prompt to save Test Plan on exit
           Product: JMeter
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: mramshaw@alumni.concordia.ca


When exiting, the following message is printed:

    Note to self, we should really prompt to save here... (bb)

I will post a suggested patch shortly.

The tricky part is deciding which object should be aware of the
'dirtiness' of the test plan (I am leaning towards the TreeModel
[as in GuiPackage.getInstance().getTreeModel()] although there
are probably better candidates).

'Save' should clear the 'dirtiness' of the test plan, although
'Save' may have only saved a portion of the test plan (is this
by design? Saving can be done at the node level; I have been
caught by this at least once).

As well, there are probably _many_ places where the test plan
should be set to dirty - but only the 'Save' can clear this
(even 'Load'-ing a new test plan might only add to the test plan).
Have I understood this correctly ? It doesn't seem to be possible
to change test plans without closing down and restarting JMeter.

As a side note, would a ThreadGroup be a candidate ? Was it
intended that there only be *one* of these per test plan ? (I know
that it is possible to have more than one, but this might be
an oversight).

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>