The Automation Hub

 Functional Regression Testing using a Hybrid Framework Combines Keyword-driven and Data-driven techniques. Likely built for Web UI automation. Breakdown: MS Access (RUNCHART Table) Test execution summary is stored in a table ( RUNCHART ). Fields like RUNID , SCN_ID , SCN_DESCRIPTION , EXECUTED_BY , etc. Tags like Regression and execution status are tracked. Indicates test case execution tracking and reporting is handled through MS Access database . Java Code (Eclipse – ScenarioStepGenerator.java ) Code is preparing and executing SQL queries to fetch test scenario steps. Interacts with tables like SCN_FUNC_BATCHING and SCN_STEPS_AUTOMATION . Implements logic to insert/update test steps dynamically. Core automation engine is Java-based and fetches test steps dynamically using scenario IDs . JDBC is used for database connection and query execution.   Excel (Object Repository) Excel file ( iDataSyncr ) is used as UI Object Repository . Fields...

  Keyword-Driven Framework Best for teams with mixed skill levels (non-coders + testers). Easier to maintain in the long run. Ideal when application changes often —you only update keywords, not scripts. Needs more time and effort to set up initially. Data-Driven Framework Best when test data changes frequently but test logic stays the same. Suitable if your team is comfortable with coding . Less complex than keyword-driven but harder for non-programmers to contribute. ✅ When to Choose What Scenario Recommended Framework Team has non-programmers Keyword-Driven Frequent data changes Data-Driven Need long-term maintainability Keyword-Driven Small team with coding skills Data-Driven Application updates often Keyword-Driven

  What is a Keyword-Driven Framework? A Keyword-Driven Framework is a type of automation framework where test steps are defined using keywords . Each keyword represents an action (like click, enter, verify) and is stored along with test data in Excel or a similar table. It separates: Test logic (in scripts) Test data and steps (in Excel or DB) That’s why it’s also called Table-Driven or Action Word-Based Testing . 🔍 Why Use a Keyword-Driven Framework? Test scripts are written using keywords , making them easier to understand. Non-programmers can design test cases without writing code. Test automation can start early in the development life cycle. Business users and testers can collaborate better using readable test steps. Common functions are reused via a shared library. Makes testing more maintainable and scalable . ✅ Benefits of Keyword-Driven Testing Easy to read and maintain test cases No coding skills needed to write test cases ...

  What is a Data-Driven Framework? Data-Driven Testing (DDT) is a testing approach where test data is separated from test scripts . It allows you to run the same test with multiple sets of input data. Instead of writing separate tests for each input, DDT lets you store data in external sources like: Excel files CSV files Databases Arrays or tables This saves time and makes testing more flexible. Example: Just like entering a student ID gives all their details from a database, DDT lets you run a test by just changing input data — the test logic stays the same. ⚙️ Why Use a Data-Driven Framework in Test Automation? Often, the same test needs to run with different input data . Writing separate scripts for each is time-consuming. DDT allows separating data from test scripts , so one script can run with many data sets. It reduces maintenance effort —only the data needs to be updated when business rules change. Helps identify the most important inputs by t...