S/W Designing ML Ops RPA Bots & Talks

If We dont ask : Why should We implement this?  then We would miss out the best alternative solution to resolve the true needs and later on We fall under the high performance losses. I have many technical leader friends who have always thoughts and fight in their minds that when choosing features for product development milestones what is the actual "needs" for specific features to implement first on high priority; This is the tricky question and one gets the right answer in right time when He / She exercises and grows with correct set of tools and techniques and or process with his / her teams and clients. To understand the clients' and teams' NEEDs (and wants),  There is an easy simple structured process -- It is called "Design Thinking"   I use to call  2D-3D technique  and am practicing this from many years. 2D means  2D iamonds technique to initiate with teams various meetings 3D means  3D imensional approach to continuously add feedback loop in ev

They say every architect has many stories to share ... Couple of my friends ask me many times to post some basics of software architecture and experiences ..so next I would be posting few articles to learn more about Software Architect + AI ML Projects + DevOps insights. Note : If You are a Software Engineer / Analyst or Senior Software Developer or in other Software Engineering role and want to become an Software Architect then welcome to my posts :)

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.

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.

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

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

Someone has well said "Communication matters" -- I would like to go further ahead. Yesterday, I went to PathMark to get some stuff. There were some schemes going on Tide (laundry detergent) with light bulbs on discount. One Customer came to customer service and started demanding he needs two bulbs free with Tide but the fact was that there was some discount if you purchase Tide with that light bulbs. The customer support guy explained the person that he could not give free two light bulbs as that was not scheme currently. Still the guy asking for free – he did not listen to customer support person and continuously telling him "I want free light bulbs". Customer Support Person explained him three or four times with his best knowledge that he could not give him but still that guy demanding. At last customer support person call to his Manager for help; Manager came and explained to the person that you got your discount and that is the scheme running currently but perso

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