> For "marketing" purpose, I would select more recent graphs for demos :)
Maybe there is some nice "demo" JMeter project that showcases these cool new things? >> modular architecture, > +1 provided it's backward compatible In some regards it might be backwards compatible, but generally speaking some things must be deprecated in order to architect better (the global configuration files / singletons come to mind). >Note I tend to prefer completing each piece of work than starting lots of ideas at the same time. But that's only me :) The Plugin Portal works, I just need to integrate a few plugins for testing and see if they hook up properly. I could also use the Plugin Portal to deliver less important plugins like MongoDB... > I'll be happy to help on PR at jmeter github Not everything can be done incrementally in a PR. But there's plenty of other incremental changes that I need into JMeter that would also help the project itself (like Maven, etc). I'll start preparing more patches next month, this month I want to release YaMeter builds. > Anyway, thanks for all your innovations ! That's pretty refreshing This is not a proof of concept, it's all functioning stuff. Some more error recovery and detection might be needed but I'd say it's basically usable. --emi On Fri, Sep 15, 2017 at 1:06 AM, Philippe Mouawad <[email protected]> wrote: > On Wednesday, September 13, 2017, Emilian Bold <[email protected]> > wrote: > >> > - I suppose you're embedding a JMeter right ? >> >> Yes, of course. Which was not easy because JMeter really expects to be >> running with full control of the VM. >> >> > - why use this old "graph results" and not more modern elements or the >> > web report ? >> >> No particular reason, I just picked something from the Add | Listener >> popup menu. > > For "marketing" purpose, I would select more recent graphs for demos :) > We must show people JMeter has evolved :) > >> >> > - Any reason to limiting it to AWS ? why not use jcloud to make it more >> > cloud agnostic ? >> >> To me AWS is the big one. I didn't want to use jCloud because I didn't >> want to have to think about how jCloud might map their concepts on top >> of the AWS concepts and debug jCloud instead of just debugging AWS's >> own SDK. In time it might make sense to code against a single API. > > > Is it that complex to start immediately with jcloud ? > I found their API pretty easy to map , at least for ypur requirement. > >> >> > - You plan to share it on github ? >> >> In time, yes. Right now this is also a poll for load testing users' needs. > > okay > >> >> Besides the cloud integration, there are some other aspects the might >> be interesting for JMeter to pursue: multi-document, > > +0 > >> >> modular >> architecture, > > > +1 provided it's backward compatible > >> out-of-the-box plugin portal. >> > >> > +1000 > I'll be happy to help on PR at jmeter github > > Note I tend to prefer completing each piece of work than starting lots of > ideas at the same time. But that's only me :) > > > Anyway, thanks for all your innovations ! That's pretty refreshing > > --emi >> >> >> On Tue, Sep 12, 2017 at 11:07 PM, Philippe Mouawad >> <[email protected] <javascript:;>> wrote: >> > Hello Emilian, >> > Very Interesting and nice for a prototype, few notes/questions: >> > >> > - I suppose you're embedding a JMeter right ? >> > - why use this old "graph results" and not more modern elements or the >> > web report ? >> > - Any reason to limiting it to AWS ? why not use jcloud to make it >> more >> > cloud agnostic ? >> > - You plan to share it on github ? >> > >> > Thanks for sharing >> > >> > Regards >> > >> > On Tue, Sep 12, 2017 at 10:02 AM, Emilian Bold <[email protected] >> <javascript:;>> >> > wrote: >> > >> >> Here's a video with a working prototype of my Amazon EC2 integration for >> >> remote tests: https://vimeo.com/233443690 >> >> >> >> --emi >> >> >> > >> > >> > >> > -- >> > Cordialement. >> > Philippe Mouawad. >> > > > -- > Cordialement. > Philippe Mouawad.
