Return-Path: X-Original-To: apmail-jmeter-dev-archive@minotaur.apache.org Delivered-To: apmail-jmeter-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6ABE31728A for ; Thu, 30 Apr 2015 12:49:55 +0000 (UTC) Received: (qmail 51285 invoked by uid 500); 30 Apr 2015 12:49:55 -0000 Delivered-To: apmail-jmeter-dev-archive@jmeter.apache.org Received: (qmail 51254 invoked by uid 500); 30 Apr 2015 12:49:55 -0000 Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jmeter.apache.org Delivered-To: mailing list dev@jmeter.apache.org Received: (qmail 51242 invoked by uid 99); 30 Apr 2015 12:49:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2015 12:49:54 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for dev@jmeter.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2015 12:49:50 +0000 Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 34B30437C7 for ; Thu, 30 Apr 2015 12:49:29 +0000 (UTC) Received: by iejt8 with SMTP id t8so65880714iej.2 for ; Thu, 30 Apr 2015 05:49:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mWvKMPo7cypJOjm6JpbUhM90CgwApZQvKxTIf/d3lwc=; b=wSg72YlSU94AcKZ0IscXo3GsdB5xVZjUeN1XGdesN/MrCWAVV5H+KygWFv6q5XIPdy j1O3oBh1OQemLhNpn2EdAmDTb0HVBw2crNP8dCJstG/w55XyAYoTXQapLwYmXfTPlARH bQJQspbSPsSKhXAHItma3RFfUcS8gumV4PJm+NNehU4P0eo0GdFDjxdUIOexq5Wg2EiS mzsIorWreDqk7O1fk2uEST5ulirKpGoemIZK8uwBpyaBxXFp9LfIlom/uBRho7zR/xFt tmtxBE9cJy/QBp4w1k9wruyxMau98Ky8l3R/pk+myWy5wjtcclFugDRegWd1L+WnG7Mc s0UA== MIME-Version: 1.0 X-Received: by 10.50.85.43 with SMTP id e11mr3224267igz.15.1430398168708; Thu, 30 Apr 2015 05:49:28 -0700 (PDT) Received: by 10.107.46.157 with HTTP; Thu, 30 Apr 2015 05:49:28 -0700 (PDT) In-Reply-To: <553E0EBC.4090601@ya.ru> References: <553E0EBC.4090601@ya.ru> Date: Thu, 30 Apr 2015 14:49:28 +0200 Message-ID: Subject: Component adding hotkeys From: Philippe Mouawad To: "dev@jmeter.apache.org" Content-Type: multipart/alternative; boundary=089e0149bdf2bbba090514f086de X-Virus-Checked: Checked by ClamAV on apache.org --089e0149bdf2bbba090514f086de Content-Type: text/plain; charset=ISO-8859-1 Hi, I think it's a nice idea, we have same the same feedback. For me it should be in core once linux issue is fixed, what about tested platforms: - Windows 8? 7 ? - Linux - Mac OSX ? which os ? Regarding other questions, answers inline. Regards On Monday, April 27, 2015, Andrey Pokhilko > wrote: > Hi, > > I have colleagues that do heavy JMeter scripting and they come with idea > to speed-up the process: have hotkeys to add JMeter components to test > plan. Using a hotkey eliminates the need to walk through context menus. > As always, Pareto principle states that 80% of a time people use 20% of > components, so small set of hotkeys would cover most of situations. > > I have implemented this feature as Ctrl+0 .. Ctrl+9 hotkey set, with > components configurable through properties. Components are added as a > child of current position, if possible, or a sibling at the nearest > possible scope. I provided my colleagues with patched JMeter and they > found the feature working smoothly. > > Pull request for easy review is here: > https://github.com/apache/jmeter/pull/16 , I will create bugzilla for > this when needed. > > As always I ask if other committers support adding this into main JMeter > codebase or not. > > Some notes/questions from my side: > > * Where is appropriate place in the docs to document this feature? Somewhere where Search Feature and templates are documented > * Are defaults good? What are most used JMeter components? I would remove or put them at end: View Results Tree User Defined Variables Test Fragment as although popular you rarely add more than 2 or 3. I would add : - Css/JQuery extractor - Jsr223 Post processor - Test Action for the timer discussion we had - JSR223 Pre processir -Debug Sampler > * Is there a way to specify component names in properties instead of > classes? There are name shortcuts in saveservice.properties > * On my Linux Ctrl+9 does not work for some reason... I wonder if > somebody knows why. > > -- > Andrey Pokhilko > > -- Cordialement. Philippe Mouawad. --089e0149bdf2bbba090514f086de--