Hi, What's the next steps on this ? Regards On Sun, May 10, 2015 at 7:11 PM, Felix Schumacher < felix.schumac...@internetallee.de> wrote:
> Am 07.05.2015 um 02:09 schrieb Vladimir Sitnikov: > >> As far as I am aware, there has been little or no demand for this on >>> >> the user lists. >> >> How do you handle usability issues? >> Do you suggest all usability issues are out of scope of JMeter? >> >> I think users are just not aware of the possibility of better life, >> thus you do not see requests >> >> "skip rows in CSV file" is a pure usability issue. It has manual yet >> painful WA. It has even automatic WA (e.g. some loops in jmx plan). >> However, it is just an additional pain for newcomers. >> > I think "skip rows in CSV file" was asked for before, but mostly in > multi-node setups, where the question was, "how can I read in values, that > are meant to be for this specific node only" > > Maybe we could try to solve those two problems in one go. One possibility > would be to add a while loop to the CSVDataSet class where the values are > actually read and use a condition to decide, wheter the read-in values > should be emitted. > > For the skip-row case, we could decide on a line-number variable (which > probably would have to be added), in the multi-node setup, we could use a > node identifier. > > The condition could even be user submitted for use cases we were not > thinking about yet. > > Now that I think of it, we could even use it to "shuffle" the input, by > checking on a random variable. It would probably be not very efficient, but > the third use case, that people ask for often. > > Regards > Felix > > > >> if selected, then check if the marker file >>> is present, and if so skip that many rows. >>> >> I do not follow you. Initially you said existing CSV Data Set should >> not be extended: "Do you think JMeter core should handle the case -- >> no". >> Now you suggest improving it. >> >> Note that the StringFromFile function has a feature which allows the >>> use of multiple input files that can be used in sequence >>> >> I do not see how it is useful in current context. >> When I said "5-10 input files" I meant "5-10 thread groups with each >> having its own input file". >> >> Vladimir >> > > -- Cordialement. Philippe Mouawad.
