S/W Designing ML Ops RPA Bots & Talks

These are very highly scalable Bots empowered by PaaS solution with MLOps and DevOps pipelines. To setup and make these simple deployments in your premises, We have RPA, MLOps & DevOps Tools, Frameworks and Techniques to apply for corporates. Please, feel free to contact me for further progress in your project or any consultancy.

Headless Testing means testing without GUI. There are couple of testing such as Unit testing, Component Testing, Module Testing, Integration Testing, CC (Code Coverage of Condition) Testing \ Base Path Testing, Mutation Testing, DB Testing, API Testing and or Web Service Testing may fall under Headless Testing. As you can see most of testing are white box or gray box testing. In XP\XT (Extreme Programming\Extreme Testing) of agile, It is the first step in implementing story. Open Source tools such as Watir, Warin, Junit, Nunit, HTTPUnit, HTMLUnit, WebTest Canoo, Fitness, Selenium RC and scripts like shell, vbscript, groovy, SoapUI (and some good paid tools Autoczar, QTP, SilkTest, TestComplete) are helping to automate this type of testing and play effective and efficient role in the QA feedback of product lifecyle. It actually tells us where is the issue. So, always say "Yes" to Headless Testing in your project.

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