jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [jmeter] FSchumacher opened a new pull request #595: Add freestyle naming scheme to proxy samples
Date Sun, 31 May 2020 14:15:00 GMT

FSchumacher opened a new pull request #595:

   ## Description
   This is a slightly different approach to naming samples that are recorded via the proxy
that has been proposed in #571.
   ## Motivation and Context
   I think as we add another scheme to naming recorded samples, others will want their favourite
naming schemes, too. So in this PR I try to anticipate that by adding a format string that
can be used to go really wild on your naming preferences. (The newly added *suffix*-mode can
be expressed through the format string, as well as the older modes *prefix* and *transaction*)
   The PR #571 has one other feature, that is *not* implemented in this PR. Namely the addition
of setting starting numbers for recorded samples. I think that should be added in another
feature/PR. It is of course possible to add it later with this approach, too. 
   ## How Has This Been Tested?
   <!--- Please describe in detail how you tested your changes. -->
   <!--- Include details of your testing environment, tests ran to see how -->
   <!--- your change affects other areas of the code, etc. -->
   Currently it has only been tested via GUI. No tests have been added.
   ## Screenshots (if appropriate):
   ## Types of changes
   <!--- What types of changes does your code introduce? Delete as appropriate -->
   - New feature (non-breaking change which adds functionality)
   ## Checklist:
   <!--- Go over all the following points, and put an `x` in all the boxes that apply.
   <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help!
   - [x] My code follows the [code style][style-guide] of this project.
   - [ ] I have updated the documentation accordingly.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message