Job Title:
ACCELQ Test Automation Architect
Company: TribolaTech Inc
Location: Vellore, Tamil Nadu
Created: 2025-08-22
Job Type: Full Time
Job Description:
looking for immediate joiners or who can join in max. 30 days100% Remote Role Permanent position with TribolaTech Job Title: ACCELQ Test Automation ArchitectRequired: 3+ years of experience in ACCELQ Platform architecture and platform maintenance experience at an enterprise level 10+ years of experience in automation testing Strong knowledge ofTest Data Management , API usage, andDevOps integrationsRole Summary: This person needs to have deep technical knowledge of the ACCELQ Platform to maintain the platform across the enterprise. This person will support the Test Automation Design Specialists by assisting them in determining the best way to apply ACCELQ functionality to test automation designs for consistency across all products and teams. This person will also directly interface with ACCELQ Inc. for support questions on the ACCELQ Platform and contribute product ideas to advance the out-of-the-box functionality of the ACCELQ Platform to best meet Majesco’s needs. This person will also guide theenterprise-wide rolloutfor Majesco and help create a scalable structure for test development using the ACCELQ Platform. Responsibilities: Tool Feasibility Mapping With Respect to Insurance domain and Majesco’s expectation (with respect to current limitation with iTAF/Serenity BDD – to be explained by Majesco resources) - Identify where the ACCELQ Platform excels and where limitations exist (e.g., dynamic data sets, multi-role sessions). Help showcase Pilot Project failures (if any) clearly (e.g.: inability to simulate Time Travel) ACCELQ Framework Setup Define and configure reusable asset structures (Contexts, Actions, Suites). Implement a scalable Git branching strategy, simulate customer-level branching (50+ variants). Set up API and DB integrations, batch command triggers (e.g., Billing Night Jobs). Test Data Design Implement test data abstraction for easier reuse across different modules or clients. Define Reusability Standards Ensure all pilot work is built on reusable blocks—not hardcoded single-use assets. Establish coding/naming conventions, folder structures, and governance models.