ImpactQA

PowerSchool, a Vista Equity firm, is a recognized leader in Talent  Management solutions specifically designed for Higher Education, Government and K-12. PowerSchool helps schools and districts efficiently manage instruction, learning, grading,  attendance, assessment, analytics, state reporting, special education, student registration, talent, finance, and HR. Today,  PowerSchool is proud to be the leading provider of K-12  education application technology supporting over 45 million students in over 70 countries.

Business Requirement

The customer had acquired a couple of companies and was redesigning the products that were to be put in the market in a quick time. Also, the suite of flagship products that company-owned were never tested and hence the business team was not sure of the quality of the products being used by more than 50 school districts across US and Canada. The performance of the products was a concern and security of PII  data was also extremely important.

ImpactQA Solution

• ImpactQA Team is the QA partner with the company from last 4+ years to put together the QA/Automation approach that could be replicated across projects.
• Following approach was taken:
• Functional KT (mix of onshore and offshore) to ensure quick product learning
• Established QA processes and tools at the beginning of the project
• Automated the functional scenarios of the application using RBT Matrix
• Divided the teams into Functional (Automation + Manual), Non-functional, VAPT  (Security) and Technical Testing groups to extract maximum ROI
• Regular scrum meetings to stay on top of burning issues and providing resolution
• Currently, 40+ QA people are engaged across 12 products
• X-trained 30% of the team in at least 2 products to cater to spikes in testing
• Achieved 80% automation of all products features
• Created documents/user manuals of all products that are being used by sales and  development teams
• Functional Tools Stack: BDD (Cucumber) Selenium WebDriver with Java, Ruby with  Capybara, Geb with Groovy using Spock framework, BDD (SpecFlow) with Selenium  WebDriver C#, API (SOAP UI)
• Performance Tools Stack: JMeter, Load Runner

GTreasury, which is the leading innovator of integrated SaaS treasury and risk management solutions for the digital treasurer. Developed using the latest technology, GTreasury helps empower organizations on their path to the strategic treasury, by enabling total visibility into their cash, liquidity, payments and financial risk management.

With enterprise clients spanning North America, EMEA, and APAC, GTreasury is headquartered in Chicago with offices in London, Manila and Sydney, Australia. The application has multiple modules to be manually tested such as:

• Accounts
• Funds Transfer
• Beneficiary Management
• System Settings and many more

Tools Used: JIRA, ZEPHYR,  TESTRAIL, and CONFLUENCE

IQA takes care of the Quality of Benchmark Analytics application. IQA Team gets Automation Execution from Benchmark on a regular Basis for the Regression and Functional Testing on different environments, OS and Browsers. Our adept team has covered the different types of Automation testing like Functional Testing [Web & Mobile], Regression Testing and Cross Browser Testing.

The Benchmark Blueprint is a multidimensional Police Force Management and  Early Intervention solution for transforming  complicated administrative structures to a  simple, holistic and wellness-based  approach to policing:

• Benchmark  Management System™ — A proactive tool that captures and organizes all officer performance data in one platform.
• First Sign Early Intervention™ — A  revolutionary Early Intervention System that analyzes data to detect “first signs”  of need for early, preventative intervention.
• C.A.R.E. | Case Action Response Engine™— A first-of-its-kind system that provides customized officer support with specific-  case action steps Our mission is to transform police administration through a single-source software platform that provides a comprehensive, 360-view of every officer — in police departments of every size.

B U S I N E S S C H A L L E N G E

• In order to cater their multiple clients/agencies and to speed up the time to market, they wanted to automate their regression suite for various agencies.
• Since they are continuously adding new clients/agencies so also wanted a solution which can cater to both existing and upcoming agencies in short span of time.
• These different police agencies functionalities are configurable so a solution was required which can reuse the existing features and can plug and play for next agency with some minor modifications helping to speed-up the automation process.
• Need to provide a common solution supporting web-based application on different browsers and mobile resolutions as well as the responsiveness of the application.
• Since the existing product team was not much aware of the automation and its process so there was a  need to propose the complete automation process to fit in the existing development life cycle.

Our solution:

• Developed the entire framework using  Selenium WebDriver, Java, TestNG,  Cucumber, Maven.
• Behavior Driven Development was adopted to help reuse existing manual test cases.
• Framework solution was used to cater to both  desktop and mobile browser-based  applications
• In order to speed up the automation process, we developed the re-usable components and methods which were just plugged and play across agencies.
• Continuous Integration was implemented to support the auto-execution whenever any build is ready to test. Jenkins was used  to implementing the CI pipeline and was  supported the AWS EC2 instances for  execution
• The automation framework was also integrated with AWS cloud systems and the execution was triggered in the same instances.
• Parallel execution was implemented to speed-up the execution.

V A L U E  A D D I T I O N

• The overall execution time got reduced from 5 days to 1  day
• Framework helped in validating dynamic values
• Consistently delivered high-quality tested applications
• Improved the QA & Testing Processes
• Implementation of best practice testing processes
• Standardize but customizable across applications
• High productivity and low cost by providing a solution  that has an offshore as a primary component
• Framework re-usability features helped to reduce the  scripting effort considerably
• Faster time to market and quick feedback

What is Nykaa?

Nykaa has emerged as the largest beauty destination in India with half a million happy customers and not just for their favorite brands but also for advice, updates, expert tips and videos on how to look and feel gorgeous always! With almost 850+ curated, well priced and 100% genuine brands and 1 lakh products, Nykaa prides itself for offering a comprehensive selection of makeup, skincare, haircare, fragrances, bath and body, luxury and wellness products for women and men. 

Nature of Test Conducted

The nature of the tests conducted by the team for the Nykaa Project divided among different services and areas of operation:

•Magento powered services

•UI for different platforms which includes (Web App, Mobile Site, Mobile Apps, Tablet Site)

•Cart Services powering cart-related operations and Customer Offers

•Checkout/Payment Services which handles order creation and payment handling

•OMS for pre/post order handling including customer notifications, order view, order tracking, order cancellation and order return management

•Inventory Management Service & Third Party Services Integration

Testing Scenarios-the test scenarios listed that need to be performed and verified to confirm production releases stability over different platforms:

• User Signup, Sign-In, Guest User Operations
• UI components, Profile Management, Wishlist, Nykaa Wallet
• Cart Function (Product Varieties, Cart Migration + Merging, Wishlist, Subscription Service, Reward Points)
• Offers & Coupons (includes Free Gifts, Free Samples, Discounts, Prive Customers)
• Checkout & Payments - Seamless and Non-Seamless payment
• Traffic distribution among multiple Payment Gateways
• Order state verification includes (pending, success, failure, post order processing)
• Order History (order state change, invoice, tracking while on shipment)
• Cancelling, Return & Refund Orders
• Notifications- SMS, Push & WhatsApp

Types Of Testing Covered:

• API Testing-To verify that API works as expected and meets the expectations in terms of functionality, performance, reliability, authorization, and reliability
• Functional Testing- To verify that each function of the software application operates in conformance with the requirement specification
• Performance Testing- To determine the system parameters in terms of responsiveness and stability under various workload
• Cross Browser Testing- To verify that application works across different browsers as expected and degrades gracefully
• Automation Testing- To verify production releases with minimal manual intervention by automating sanity/regression test scenarios

Tools used for Testing the Application:

• POSTMAN
• ANDROID SDK Tools
• CHARLES/FIDDLER
• JIRA & TESTLINK
• SELENIUM/GRAFANA & KATALON
• JMETER

KFC, also known as Kentucky Fried Chicken, is an American fast-food restaurant chain that specializes in fried chicken. Headquartered in Louisville, Kentucky, it is the world's second-largest restaurant chain after McDonald's, with almost 20,000 locations globally in 123 countries and territories as of December 2015.

IQA takes care of the Quality of KFC application owned by YUM. IQA Team gets Build/release from KFC on regular Occasions for the Regression and Smoke Testing on different environments, OS and Browsers. Our adept team has covered the 6 different types of testing counting Functional Testing [Web & Mobile], Cross Browser Testing, Usability Testing, Crowd Testing, Network Testing, and Interruption Testing. 

Nature of Test Conducted

This section describes the nature of the tests conducted by the QA team for KFC functionalities in Release 1 for Web App, M-site and Mobile App.

Following Tests were Performed in the Application:

• Sign in/Sign Up
• One-Click Ordering
• Home
• Deals Page
• Menu page
• Cart Page
• Checkout Page
• Browser testing
• PWA
• OTP
• Ordering Journey
• Payment Modes
• My Account
• Orders/Coupons
• UI
• Voucher
• Splash Screen

Types of Testings Covered:

Different types of Testings done by ImpactQA for KFC. It includes 6 different types of Testings:

• Functional Testing [Web & Mobile]- Here, ImpactQA was making sure that It verifies that each function of the software application operates in conformance with the requirement specification.
• Cross-Browser Testing- Here, ImpactQA was making sure that application works across different browsers as expected and degrades gracefully. It is the process of verifying your application’s compatibility with different browsers.
• Usability Testing- Here, ImpactQA was testing it with real users. Users are asked to complete tasks, typically while they are being observed by a researcher, to see where they encounter problems and experience confusion.
• Network Testing- A network performance test primarily tests the uplink and downlink speed of a network. It defines how quick and responsive a network is to user/data communication. It is done by uploading and downloading a data object from the network and measuring both upload and download speeds, throughput, successful message delivery rate and more.
• Crowd Testing- Crowd testing is basically a form of testing wherein a crowd-sourced platform is used to connect testers from around the world to testing projects.
• Interruption Testing- Interrupt Testing is a branch of Mobile Application Testing that deals with- how an application reacts to interruption and resumes to its previous state.
• Automation Testing- on all platforms (IoS, Android, Website, M-Site (both IOS & Android)
• Responsive Testing on PWA

Tools Used for Testing the Application:

Different types of Tools used by ImpactQA for KFC. It includes 3 different types of Tools.

• Android Studio
• JIRA
• LIGHTHOUSE

The approach used by IQA:

• IQA was responsible to set up complete QA Process
• The only AGILE model was followed to accomplish the testing. Multiple Sprints were created for successful testing.
• Smoke + Sanity and Regression was done as per the requirements.
• Triage Meetings were set up to fix up different bugs, Retrospective was also a part of the same.