S/W Designing ML Ops RPA Bots & Talks

Objective How to make your automation framework accessible through out all Test Environments in other sense how to make your automation objects ( scripts \ business objects ) reusable with other platforms with Automation Tools such as QTP \ Silk Test. Problem You have different test platforms such as qa:6080 like build in qa 6080 port. qa:7080 like build in integration qa 7080 port. qa:8080 like build in staging qa 8080 port. Live environment (like any production site) We need to have centralized automation script that can get access to all above platforms. Approach for problem solution • We need to create 1.Function that can read current global environment configuration which may be in .xml. 2.Start-up Script that can add / update / set current environment from .xml or any other format – you can make GUI tool or use VBScript + Excel to maintain easily. •We need to normalize all automation objects which are pointing to specific platform like filtering out all redundancy from automat

QA Automation in V-Model Low level Testing Unit Testing with NUnit (and MS Visual Studio), xUnit and HTMLUnit on Java and C# / ASP.Net plateform. HTTP Request-Response Testing with Selenium, Canoo WebTest, SOAPUI and other free-ware tools. Integration Level Testing. Components Interface Testing. Web-Service Testing with SOAPUI API Testing with WebTest Canoo \ QTP \ SilkTest Function \ Smoke Testing \ Regression Testing High Level Testing. Cross Browser \ Cross Platform Testing. GUI Testing with Tools such as Mercury QTP, Silk Test, WinRunner. Load \ Performance testing with LoadRunner. ~NV

I like to share one automation experience or in other sense the challenge I had in automation. I joined one company as an Automation Quality Analyst Consultant. It is fast growing Company. I was as a tool smith like person recommending tools for QA team to make manual testing tasks more easier\reliable and fast way. We had established freeware tools for testcase management, defect repository and qa\project process and developed test-suites for regression and smoke testing in QTP. As we all know regression test-suite is bulky one and at that time, mine was including more then 617 testcases automated and that’s why taking more than 3 hours to finish execution. I have split test scripts on functionality vise and created test batch but the problem is test batch report does not give status for each testcases in automation execution and that encourage me to develop “TM live” tool interfaced with QTP 9.1. “TM live” means Traceability Matrix on live (parallel with automation suite execution)

This article offers answers for below questions with case-study Why do we need automation s/w testing in organization? What if organization does not have fund to purchase license for expensive automation tools? In simple way, we can say the core objective of automation is helping to finish any testing\QA task more accurate, easier and faster way with less risk involved for failure. Say for example Tools like # Functional automation tools QTPro, SilkTest, Canoo, Selenium, VBMacro. # Load/Stress automation tools LoadRunner, SilkPerformer. # Cookies reader tools. # HTTP request / response reader tools. # File comparison tools. # Tesecase Management Tools. # Web Page link / image finder Tools. # Broken link finder Tools. and many other tools we can categorize in automation testing fashion to make QA Process more smoother; Automation Testing also used for Repetitive testing task activities… As a human nature, manual tester can not perform repetitive tasks more accurately comparing to mach

The principles can be defined as 1. a rule or code of conduct; 2. a general or fundamental, law, doctrine or assumption; In software domain, these principles focus lights to test engineers on software systems, how suppose to build them and how they expect to behave. Principle #1 Testing is the process of exercising a software component using a selected set of test cases, with the intent of (a) revealing defects, (b) evaluating quality. The term “defects” used in this and in subsequent principles represents any deviations in the software that have negative impact on its functionality, performance, reliability, security and or any other of its specified quality attributes. Principle #2 When the test objective is to detect defects, then a good test case is one that has a high probability of revealing a yet undetected defect(s). The test engineer expects to work as scientist does like he creates hypotheses to prove or disprove them; that is determine if the specific defect is present or