S/W Designing ML Ops RPA Bots & Talks

In this demo, we have opportunities 1. To Bind your Java application with groovy console. 2. To Automate manual steps in groovy console. 1. Bind your Java application with groovy console. //BindJavaApplication.groovy import org.netbeans.jemmy.*; import org.netbeans.jemmy.explorer.*; import org.netbeans.jemmy.operators.*; // Fire up the SwingSet2 Application new ClassReference("SwingSet2").startApplication(); // Get a reference to the SwingSet JFrame and put it into the console's script binding. mainFrame = new JFrameOperator("SwingSet") def bind = new Binding() bind.setProperty("testScript",this) bind.setProperty("mainFrame",mainFrame) // Fire up the Groovy console. def console = new groovy.ui.Console(this.class.classLoader,bind) console.run() Thread.sleep(700000) 2 . Automate manual steps in console. import org.netbeans.jemmy.*; import org.netbeans.jemmy.explorer.*; import org.netbeans.jemmy.operators.*; // Get first butt

What does It mean by "developers' false catches" ? It means those implementations or application unexpected behaviors which should not be automated with automation framework. Why those should not be the candidates for automation? It is observed that adding these kinds of requirements in automation may set short ROI for organizations but it never becomes for long terms – You may ask “why” again, below are couple of examples which put more lights on this question. Case-Study : #1 “Product Team has new requirements in build 1.2.x like objects inputs are changed with prefix or suffix strings and that affects more than 1000 automated test-case(s)” Due to limited resources and short dead line to certify build(1.2.x) of the product, Product lead comes to AFT and asks for help. He requests to update Automation Framework in such a way that manages prefix and suffix inputs and his team does not have to update their test-case(s). As part of the service team (AFT), we provided soluti

Everyone is talking about automation tools like QTP, WinRunner, LoadRunner,Silk Test, Selenium Bla Bla bla ... but Once these tools come into real practice and he\she has to automate test-case(s) with them in existing automation framework. How far we can go with our goal? This post gives opportunity to discuss on characteristics of test-case(s) while doing designing for test-case(s) in automation. Below are the couple of thoughts, I believe to have in automated test-case(s). §          Concise - Test-case(s) should be as simple as possible. i.e. Test-case(s) should not call multiple other complex Test-case(s). It should have minimum dependency. §          Self Checking – Test-case(s) should have verification steps and It should report in its results such that no human interpretation is necessary. For example, I have found in one project; team has around 1500 test-case(s) – out of more than 44% test-case(s) has steps like 1.       Open Menu Item. 2.       Enter A/C

Loading...

Some Mozilla add-ons which are worth to install to improve your performance. BetterBugzilla 0.3.4 - gives new look for your bugzilla. Sage - allows to create feed on search query of your bugzilla. Newsfox - allows to read rss feeds in web-browser email layout; if feed items update -- this will pops up and mark as unread for that item in feed; you can use this extension to point your bugzilla feed so you can get notice for all activities happening in bugzilla. ~Enjoy,NV