Tuesday, April 29, 2025

Skills

 Skills:

  1. Cloud Infrastructure, Infra Testing, Cloud Computing
  2. Guidewire-PC,CC,BC,CM, Mainframe, SQL Basics, Basic API Testing (Postman/Swagger/Java Axis2)
  3. Automation - Selenium (Java & C#), TOSCA, E2E, UAT, Functional Testing
  4. RPA Automation Testing (UiPath/Azure), Functional Testing, Mobile App Testing
  5. Service Now, Salesforce Testing
  6. Project Management, MIM, Azure Cloud, Single Sign On Testing using Azure AD for PS & GW, Browerstack Mobile Testing, Document Management System, Guidewire ClaimCenter, ESB
  7. TestNG, 
  8. ETL, Azure Cloud (Data platforms, ADF), BI Testing, Test Data Management, Program Management, Service Delivery Management
  9. SSIS, SSRS, Mainframe Testing, Pega Testing, Manual Testing
  10. SOAP UI for API Testing
  11. Database Testing
  12. Scrum
  13. ISTQB Certified
  14. Accessibility Testing, Jenkins (Basics for manual code deployment)
  15. Automation (Selenium, Java, TestNG, Cucumber), GIT, E2E
  16. Test Planning & Strategy, Integration Testing, 
  17. Automation Frameworks (BDD, Keyword Driver, POM, Protractor)
  18. Jira, HPQC, Maven, Git and bitbucket, JavaScript
  19. Business Analysis, Agile
  20. UFT Automation with VB Scripting
  21. Guidewire InsuranceSuite Associate Analyst Certification
  22. Jasper
  23. Web App Testing
  24. Mobile Automation using SeeTest Automation, Appium-Perfecto , Eggplant
  25. ServiceNow ATF
  26. Performance Tseting (Loadrunner/Jmeter), PowerBI
  27. SOA Testing (Parasoft)
  28. Excel VBA, JQL basics
  29. BI Testing (Power BI, OBIEE, Tableau)
  30. ETL Testing
  31. Devops, Release Management, AWS
  32. Business Analysis (FLMI Certified)
  33. Function point Analysis
  34. ETL (Informatica)
  35. Kofax
  36. Safe Agile Certified
  37. AWS CCP Certified
  38. SAP BI, COGNOS, PowerBI, Tableau
  39. Risk Assessment & Mitigation
  40. Embedded Device Testing
  41. Salesforce Testing (B2B, B2C)
  42. ERP Testing (Microsoft Dynamics AX and 365)
  43. CRM Testing
  44. BI Testing (MicroStrategy)
  45. ETL Tester
  46. Agile & Kanban Frameworks
  47. ERP Tester
  48. Cross browser Compatibility Testing
  49. ALM Administration
  50. JIRA Administration
  51. Adobe Experience Manager Content authoring and testing
  52. Duckcreek Claim Center
  53. Test Data Management, CA Test Data Manager, Genrocket, Informatic ILM, Delphix
  54. QlickView Testing, Hive/Impala, DVO Automation Tool, 
  55. CMS
  56. Resource Mgmt & budgeting, Project Costing & Budgeting, 
  57. Selenium Web Driver Framework ( Java, Python, Cucumber, Maven, TestNG, PyTest)
  58. Robot Framework (RIDE)
  59. DbVisualizer,
  60. HTTP(S)
  61. XML, HTML
  62. Operating Systems (Linux Flavours (Redhat, Fedora, Debian, Solaris, Centos, HP, AIX, Ubuntu), Windows
  63. Service Now ( ITSM and Asset Management)



Steps for Automation Framework setup

Steps for Automation Framework setup

Pre-Requisites:

  1. Install Eclipse using Installer. 
  2. .m2 folder is placed under location C:\users\yourlanid\.m2 (maven dependency)
  3. Enterprise_Automation_Framework version
  4. Install TestNG in Eclipse using Marketplace
Steps for Sequential Run:

  1. Mark the Test Cases which needs to be executed in all the required Test Suite excels.
  2. Import the latest framework in Eclipse
  3. Do Maven - Update Project.
  4. Select Offline and Force Update options inside Update Project.
  5. Go to the Test File that needs to executed and right-click then select Run As-TestNG Test.

Steps for sequential run using TestNG

  Steps for sequential run using TestNG

Pre-Requisites:

  1. JDK
  2. Maven is present in the system. 
  3. .m2 folder is placed under location C:\users\yourlanid\.m2
  4. Enterprise_Automation_Framework version
Steps for Sequential Run:

  1. Mark the Test Cases which needs to be executed in all the required Test Suite excels.
  2. Update/Add the module names/class names to be executed in the below mentioned section in the TestNG.xml file. Also, based on the number of modules to be executed, update the 'thread-count' value.
    testing.xml
  3. Module names/class names can be found in the framework launcher under the 'TestClassName' column.
  4. Open TestNG.xml file in eclipse and run as TestNG Suite.

Note:
Once the execution is done. The Results can be found under the Test Results for all the executed Test Suites.

Steps for Sequential Run using Windows Scheduler

 Steps for sequential run using windows scheduler

Pre-Requisites:

  1. JDK
  2. Maven is present in the system. 
  3. .m2 folder is placed under location C:\users\yourlanid\.m2
  4. Enterprise_Automation_Framework version
Steps for Sequential Run:

  1. Mark the Test Cases which needs to be executed in all the required Test Suite excels.
  2. Set Proper locations of the framework, JDK and Maven folder inside the "Selenium_Scripts.bat" present inside the Framework main folder. (Suggestion: Once this bat file is saved as per your system locations, keep its copy with you to reuse it whenever an updated framework is shared).
  3. Dependencies will store in .m2 folder
  4. Open the Launcher file Framework_Launcher.xlsm present inside the framework.
  5. Open TestSuite sheet inside Launcher and mark the TestSuite/s which needs to be executed as Yes under Execute column.
  6. From the Press the Windows + R Keys on your keyboard to open Run, and then types taskschd.msc in the Open field. Finally, click or tap on OK, or press Enter on your keyboard.
  7. In the Task Scheduler, Click on "Create Task" in Actions (Right-hand side).
  8. Give any Name to the Task in General. Then in "Triggers" tab, Click on "New" to fill the Timing for the Task.
  9. In the "Actions" tab, click on "New" and Browse to the Selenium_Scripts.bat file that have been updated in the previous steps.
  10. If you want to make any other specific settings then make those and then finally Click on "OK" in the Create Task window. The task will be executed as per the mentioned details.\

Note:
Once the execution is done. The Results can be found under the Test Results for all the executed Test Suites.

Test Automation Coding Standards & Guidelines

 Test Automation Coding Standards & Guideline

1.Introduction
1.1 Why coding standards are so important?
1.2 Overview
1.3 Assumption

2. Naming Convention
2.1 What is naming convention?
2.2 Why use a naming convention?
2.3 General Naming Guidelines
2.4 Naming Variables
2.5 Naming Exception Objects
2.6 Declaring Local Variables
2.7 Naming Classes and Interfaces
2.8 Naming Methods

3. Comment Standards
3.1 Implementation of Comment Format
    3.1.1 Block Comments
    3.1.2 Single-line Comments
    3.1.3 Single-line Comments
    3.1.4 End-of-line Comments

4. Function/Method Standards
4.1 Function Name
4.2 Naming Accessor Member Functions
    4.2.1 Getters
    4.2.2 Setters
4.3 Constructors
4.4 Function Header
4.5 Internal Documentation
4.6 Function Complexity
4.7 Function Structure

5 Indention

6 Automation Script Standards

7 General Guidelines

8. Document Control


6 Automation Script Standards

Folder/package structure should be created based on the functionality/purpose of the scripts/files present in the respective folder.

For Example,

src\Project\Component: This package should contain all the java files related to objects of the Component pages.

FunctionLibrary: This package should contain all java files related to global functionalities like EnvironmentVariables.java, Utilities.java (re-usable functions), SpreadSheet.java etc.

Examples:

EnvironmentVariables.java -> This java file is used to maintain environment set up for the overall projects.

Utilities.java -> This java file should contain all methods which are common across the application.

SpreadSheet.java -> This java file should contain functions definitions required to operate excel files.


Performance Test Plan

 Performance Test Plan


  • 1.1 Performance Test Objectives
  • 1.1.1Performance Deliverables
  • 1.2. Performance Testing Process
  • 2.Project Overview
  • 3.Scope
  • 3.1In-Scope Items
  • 3.1.1 Non Functional Requirements
  • 3.2 Out of Scope
  • 4.Test Risk/Assumptions/Constraints and Dependencies
  • 4.1Test Risks and Mitigation
  • 4.2.Assumptions
  • 4.3.Constraints
  • 4.4.Dependencies
  • 5.SIT Performance Testing Approach
  • 5.1.Performance Test Approach
  • 5.1.1 High Level Testing Approach
  • 6.Workload
  • 7.Test Data
  • 8.Test Environment
  • 8.1 Test Environment Diagram
  • 8.2 Test Environment & Applications Details
  • 8.3 Performance Monitoring Setup
  • 8.4 Performance Testing Tools and Best Practices
  • 9.Entry and Exit Criteria
  • 10.Defect Management
  • 11.Test Schedule and Milestones
  • 12.Appendix
  • 13.Document Control

  • 8.4 Performance Testing Tools and Best Practices
    Performance center/load runner tool will be used to create scripts and execute the performance test runs.
         Test Phase:  Test Design
         Tools Required:  OpenText Vugen 12.6, vugen 202, JMeter

         Test Phase:  Test Execution
         Tools Required:  Performance Center 12.6, LRE SaaS
        

         Test Phase:  Result Analysis
         Tools Required:  OpenText Analysis

         Test Phase:  Defect Management
         Tools Required:  HP ALM, JIRA

Technical Skills

 Technical Skills:

  • Non-Functional Requirements Analysis
  • Technical Coordination: Non-Functional requirements translation into scope
  • Technical Coordination: Environments
  • Code Management: Bit Bucket/GIT
  • Programming & Scripting:  C++, C, C Sharp, other
  • Programming & Scripting: Java
  • Programming & Scripting: Python
  • Programming: SSIS/SSR
  • Scripting: Unix/Linux Shell Scripts
  • Scripting: Visual Basic
  • Test Automation System Analysis and Evaluation
  • Test Automation Tool Selection
  • Test Automation Framework selection and development
  • Mobile platform tools and configurations (Appium, Xcode and Android studio)
  • Performance Testing Conceptual Knowledge
  • Performance Test Strategy
  • Performance Test Plan
  • Performance/Load Scenarios
  • VU Gen
  • Performance scripts Maintenance
  • Performance test tools:  Performance Center, Load Runner, Jmeter
  • Performance Test Reporting & Analysis
  • Performance test innovation
  • Data Integrity
  • Revers Engineering
  • Data Profiling
  • EDM - Enterprise Data Management
  • ETL - Extract Transform Load
  • MF Experience
  • RDMS (MSSQL, Oracle, DB2)
  • DataStage

Functional Skills

 Functional Skills:


  • Document Review 
    Use of Analytical skills in reviewing documents
  • Functional Test Strategy
    Sill of determining and documenting Test Strategy and its contents
  • Test Plan
    Document detail plan and test approach
  • Requirements Analysis
    Clear understanding of requirements and identify gaps
  • Test Objective Matrix
    Identify test scenarios
  • Test Case Design
    Design step by step test case with Pre-conditions and expected result
  • Create Traceability Matrix
    For adequate coverage
  • Testing Methods
    Familiarity of White Box or Black Box Testing
  • Test Data Creation/Identification
    Familiarity of understanding data required on the project for testing
  • Creating Test Summary Report
    Test Closure and Signoff
  • Test Status Reporting
    Accurate, Clear and Complete reporting of the testing status


Monday, April 28, 2025

Automation Testing

 

Software Testing Tools

 Software Testing Tools 


Production
  • Broadcom - CA TDM Data Manager (Masking, Sub-Setting)
  • Application Testing Suite
  • Selenium
  • Morae
  • UFT
  • SOAPUI
  • JMeter
  • Performance Center
  • ALM (Load Runner)
  • BrowserStack
  • Grype
  • Xray
  • Sonarqube
  • Dynatrace
  • Jira
  • Confluence
  • Maven
  • Atlassian Jira and Confluence Cloud
  • ETL, Test Automation Capabaility
  • Testing Data Virtualization - Delpfix/CA vTDM
  • Test Automation of MF and Kofax Testing with UIPath
  • Maze
  • Microfocus Cloud SaaS for HP ALM and LRE

QA Websites & Youtube Channels

 Websites:

https://www.softwaretestingmentor.com/

https://www.softwaretestingmaterial.com/

https://www.softwaretestinghelp.com/resources/

https://www.guru99.com/software-testing.html

https://www.geeksforgeeks.org/software-testing-tutorial/

https://www.h2kinfosys.com/blog/scenario-based-software-testing-interview-questions-and-answers/

Scenario Based Software Testing Questions & Answers

Scenario Based Software Testing Questions & Answers

  1. How will you test customer registration web page?
  2. How will you approach testing for any requirement or user story?
  3. How will you overcome the challenging of not having documentation for testing?
  4. Why is regression testing in Agile Development challenging and how will you handle it?
  5. What are cookies and how to test cookies?
  6. If the software and one of the code module is modified. Will you re-test the whole application or just test the functionality associated with that module?
  7. Do you agree that the tester should study design documents for writing test cases?
  8. What are some of the testing tools that you have used in your past projects?
  9. What will be your approach to create a Test Case?
  10. Can you explain few scenarios for testing pagination?
  11. Can you write some test scenarios for Radio button?
  12. How do you ensure that all requirements are covered by testing?
  13. How will you test the application which requires integration with third party systems/APIs which are not available?
  14. What will be your approach to test the responsive web based application?
  15. You have large number of test cases to execute but limited timeframe to complete testing? What will your approach to ensure proper test coverage?
  16. You are managing a team of 5 testers which is not co-located, how will you ensure team productivity?


Software Testing

 Software Testing:

  • SDLC/STLC
  • Types of Testing
  • Testing Techniques
  • Agile Methodology
  • Bug Tracking Tools
  • Test Management Tools

Programming Languages

 Programming Languages

  • Java
  • Python
  • Java Script
  • C#
  • SQL

Web Automation Testing

 Web Automation Testing

  • Selenium
  • Cucumber
  • Cypress
  • Katalon
  • Maven/Gradle
  • Git & Github
  • GitLab, Bitbucket
  • Jenkins
  • Docker

API Testing

 API  Automation

API
  • Postman
  • SoapUI
  • RestAssured (Automation)
  • Karate API
  • Insomnia
  • Bruno
  • Testfully

Mobile Testing

 Mobile  Automation

Mobile
  • Appium

Performance Testing

 Performance & Security Testing

  • Performance
  • JMeter
  • Load Runner

Security Testing

 Security

Penetration Testing

  • Burp Suite
  • Vega

Cloud Testing

 Cloud Testing

  • AWS
  • SauceLabs
  • Azure
  • Google Cloud

Codeless Tools

 Codeless Tools

  • RPA
  • TOSCA
  • TestRigor

Roadmap to QA/Automation Tester

 Roadmap to QA/Automation Tester 

Software Testing:

  • SDLC/STLC
  • Types of Testing
  • Testing Techniques
  • Agile Methodology
  • Bug Tracking Tools
  • Test Management Tools
Programming Languages
  • Java
  • Python
  • Java Script
  • C#
  • SQL

Web Automation
  • Selenium
  • Cucumber
  • Cypress
  • Katalon
  • Maven/Gradle
  • Git & Github
  • GitLab, Bitbucket
  • Jenkins
  • Docker
API + Mobile  Automation
API
  • Postman
  • SoapUI
  • RestAssured (Automation)
  • Karate API
Mobile
  • Appium
Performance & Security Testing
  • Performance
  • JMeter
  • Load Runner
Security
  • Burp Suite
  • Vega
Cloud Testing
  • AWS
  • SauceLabs
  • Azure
  • Google Cloud
Codeless Tools
  • RPA
  • TOSCA
  • TestRigor



BrowserStack Testing

 Test any app: Web, mobile & enterprise Any type of testing:  Functional |  Cross-browser & real device | Accessibility | Visual | P...