S/W Designing ML Ops RPA Bots & Talks

However , MLOps goes parallel along with AIOps + DevOps. I had done couple of Open Source #MLOps and #AIOps projects We have applied tools and techniques for the AIOps, MLOps & DevOps ,  To setup and make these setup in your premises, Please, feel free to contact me on further progress in your project or consultancy.

To have these setup in your premises with MLOps Tools and Techniques, Please, feel free to contact me on further progress in your projects.

This is what happens when there are No Integration Tests in production pipelines 🤣 Let's encourage more  integration tests in our projects :)

Someone has well said ..  “To delight customers, one should continuously innovate, implement, test it, fix it, test it, release it and do all again and again.” To do so more efficiently, I would like to add Software AG Agile Tester (SAT).  It  offers various testing solutions to accelerate agile feedback loops. Currently Agile Tester (SAT) is being used in more than  52,000+ Tests by more than 21+ Product Teams . It is under Beta release for Clients. It has two major components 1.       SAT Server - Central Repository for Test Scenarios and Test artifacts. 2.       Tools 1.       SAT Client 2.       Recorder and Playback [Snapshot : #1] Developer or QA can use “Agile Tester” (SAT) to move testing process earlier in the development cycles so that We can prevent errors rather than detecting them later;  Here We shift testing activities closer to the build process and proactively test applications to uncover defects and so Product Teams (enterprise) can accommodate releases faster.

JavaScript in Webdriver Sometimes Webdriver does not help to find objects and their properties. We can develop Javascript functions and inject them via Webdriver.   It is good to develop Javascript and inject via Web driver to validate SVG Canvas objects like Charts. Webdriver provide a “JavascriptExecutor “class for executing java script. First you need to create “JavascriptExecutor” class object. JavascriptExecutor js = (JavascriptExecutor) driver; Now call “executeScript()” method by passing java script code as a argument. js .executeScript(“java script code”) Here are some more examples. String readyState = (String)js.executeScript("return document.readyState"); String title = (String)js.executeScript("return document.title"); String domain = (String)js.executeScript("return document.domain"); WebElement el   = (WebElement)js.executeScript("return document.getElementById('rentc');"

The Verifaya platform is the the fastest and easiest way for companies to test mobile & web enterprise apps across wide set of devices and environments. You can see the results in hours not days.  Verifaya helps to extend, modernize & integrate with your existing systems, test apps anywhere on any devices in your organization, manage them centrally and test them instantly with one click.  Verifaya was founded in 2005 and since our inception, we have delivered automated software testing solutions to companies of all sizes – from startups to Fortune 500 companies. To get more info or any help, drop your comment or email me.

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

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...

I had a challenging project to automate Java Objects on the fly – sharing some part of it. Challenges I faced 1. Objects which are built on top of JMesa , JQuery, JSON and AJAX technology -- are not recognized by professional automation tools (such as QTP and SilkTest). 2. How to automate Dynamic Graphs which are implemented with technologies like Flotr and 3D Canvas. 3. Web application needs to automate with cross-browsers ( IE 6.0+ , FF 2.0+ or Safari 2.0+ ) It focus objects screen rendering issues which are different from one browser to other. How can we overcame • Challenge #1 and #2 can be resolved with below automation approach. Verify HTTP Responses when user does some actions like objects fire specific AJAX calls; We simulate these AJAX calls ( HTTP requests ), capture valid\expected response, set them as baseline and in QA loop we simulate user actions again with automation, capture actual response and compare with baseline. • Challenge #3 can be resolved with below automatio

Here is I want to share qa project management checklist I used in real scenarious. Project Initiation Prepare System Test Estimates Define System Test Approach Define Testing Scope Prepare DRAFT System Test Plan Review System Test Plan Prepare Test Schedule Request Test Resources Request Business Expert Request Management Support Request Environment / Technical Support Request Facilities (Desk, Chair etc.) Setup Test Project Folder Revise Test Estimates Define Entrance / Acceptance Criteria Agree Communication Channels Agree Reporting Procedures, Methods and Frequency Define Exit Criteria Design Release Notes Template Test Preparation Agree Builds / Drops Schedule and Contents Agree Release Notes Contents and Format Agree Error Management Procedures Define System Test Roles and Responsibilities Assign Test Roles and Responsibilities Assign Test Case Preparation Primary Responsibilities Assign Test Case Preparation Secondary Responsibilities Prepare High Level Test Cases Prepare Low Lev

Last week, one of my friend needs some help to establish Project\QA workflows on Jira (Atlassian) So here I am happy to share some of my odd solution. Project Flow problems or hard to implement in Jira were * One stage splits with multiple stages in flow. * More than one stages merges to one stage. Here We have Brainstorming splits to UT - ST stage and Dev Review - QA Review merges with Review stage executed by System Group Members in project flow. One issue splits with more than one issues, can also be implemented with sub-tasks feature but it may not push next stage in the project flow as the project progresses; all sub-tasks are linked to the parent task only, may not execute inline flow; may not give more control to administrator\lead and may be more complicated to maintain. Sub-tasks may not be merged to one task on transitions after Dev. Review / QA Review merges to Review stage. Core objective is to implement flow that anyone can see each stage of the flow and can

These old days' automation techquies should be replaced with #ML based automation,  Isn't It ? :) If You have such automations that causing lots of issues then let's talk on how You can come out from your nightmare pains.