Learn Enterprise Level Automation program from Next Generation Automation helps QA Engineers to master test automation development in support with Next Generation Automation Founder, Ankur Chaudhry.
Program Salient features as below:
Program give QA Engineers enterprise level Automation experience
Phase 1 of Program lets QA Engineers build framework architecture in a multi-threaded environment using Java as a programming language and Selenium as an automation API.
Program let QA Engineers understand pain areas which automation engineers face while at work and how to fix the same.
Program gives real world Automation Experience to QA Engineers and all automation exercises covered during program based on enterprise level automation scenarios
Program helps QA Engineers build a developer mindset. How to approach complex business flow for automation and what should be QA Engineer design and coding approach while at work.
Successful course completion and evaluation gives Star awards to all certified members.
Star awards helps QA Engineers to brand them self both at international & domestic level and help them chase Overseas QA Automation jobs at very attractive salary packages.
Block Diagram Learn Enterprise Level Automation program as below:
Image shown above subject to copyright of Next Generation Automation and
for learning purpose only.
Learn Enterprise Level Automation Program divided into multiple sections to reduce the complexity and build scale able automation architecture as per enterprise needs.
Section 1: Execution Engine
This will be the start point for test scripts execution and execute test scripts in multiple Java threads. Each test class will be assigned 1 Thread for execution at run time by Execution Engine.
Multi threading feature helps executing huge numbers of test scripts in a smaller time frame without compromising test quality.
Section 2: Test Data Factory
Modern business applications require a lot of data to be entered or verified.
Such test data requirements will be served by the Test Data factory design pattern developed by NGA.
At this point multiple storage formats are already integrated with developed architecture that includes Excel, Ini and MySQL.
QA Engineers depending on project requirements can scale the test data factory to other storage formats as well in future.
Section 3: Test Container
Test container section holds actual test scripts that need to be developed as per application functionality.
This section is specific to projects assigned to QA Engineers. Learn Enterprise Level Automation program let QA Engineers build test scripts for NGA Website. Later based on expertise gained, they can automate any other business application as part of working live projects.
Section 4: Browser Factory
Browser Factory will be the core of Automation Architecture and determines which browser to consider for test execution and how to maintain driver instances in case of multi-threading based / parallel test execution.
Also, it sets up initial project environment like initializing Logging, Reporting and Configuration Files. Browser Factory independent of application under test and will be a reusable component across multiple applications under test.
Section 5: Business Layer
Business Layer holds actual business workflows that need to be developed based on Application functionality.
Learn Enterprise Level Automation Program takes into consideration NGA business workflows as part of this layer. This layer is specific to the project and depending on the application under test this layer can be developed.
Section 6: Logging
Logging keeps a log of all test execution steps and helps QA Engineers debug the test scripts for any failures and verify whether results generated as per written test scripts or not.
Log files keep updating in real time based on test steps execution both at development console and text file format.
Section 7: Reporting
Reporting section generate test scripts pass and fail count in real time along with test dashboard creation in HTML format.
If test execution in parallel, this module will fetch the results from all test scripts and generate consolidate test execution report once entire test execution get completed.
For each thread class, separate report instance assigned at run time to capture test execution steps along with failures or exceptions generated from application if any.
Section 8: Page Classes
Page classes hold information about specific web pages.
This includes building page elements along with page interaction methods. Page Class layer specific to project and depending on application under test this layer can be further developed.
Section 9: Utility Classes
Utility classes hold information about common utilities methods required for test script execution. Common Utilities include Excel Reader, Data Base Reader, Element Finder, Working with Frames, Buttons, Check Box, Drop Down components of application and many others.
Utility classes independent of application under test and will be a reusable component across multiple applications under test. Both utility classes and Page Classes at end of program are going to integrate with Spring Dependency injection Framework to provide ease of test scripts development and without worry to initialize every page and utility class object during test execution.
Overall framework architecture and course contents developed keeping in mind IT Industry latest testing trends and development in Automation field over the last few years.
Architecture developed as part of a program subject to upgrades in future even after its Phase 1 release.
Interested QA Engineers can subscribe for program as per below link:
For any details, you may connect with NGA at firstname.lastname@example.org.
Founder, Next Generation Automation
Building better QA for tomorrow