Boozang from the trenches learn test automation with boozang in an enterprise environment
Test Automation is a key aspect of delivering high-quality software and reducing time to market. Several tools and approaches are available today, each with its own constraints and specificity. This book introduces Boozang, a codeless web automation tool, using a real-life enterprise project as sour...
| Other Authors: | |
|---|---|
| Format: | eBook |
| Language: | Inglés |
| Published: |
New York, New York :
Apress Media LLC
[2023]
|
| Subjects: | |
| See on Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009711796506719 |
Table of Contents:
- Intro
- Table of Contents
- About the Author
- About the Technical Reviewer
- Acknowledgments
- Foreword 1
- Foreword 2
- Introduction
- Part I: Testing Web Applications in an Enterprise Context, Why Boozang
- Chapter 1: Web Test Automation in an Enterprise Environment
- Common Test Automation Challenges
- Challenge N1: Culture
- Challenge N2: Skills and Resources
- Challenge N3: Technology
- Challenge N4: Long-Term Maintainability
- Test Levels, Test Types, and Testing Roles
- Test Levels
- Test Types
- Testing Roles
- Test Environments
- How We Manage Test Environments
- Managing Test Environment in JIRA with the GoLive Add-on
- Test Automation in Agile Development
- Test Automation ROI, Theory and Practice
- Chapter 2: Selenium: Best Practices and Pain Points
- Locators and Page Objects Pattern
- Browsers and WebDriver Compatibility
- Timing and Waits
- Data Management
- Reporting and Script Readability
- Development Skills
- Chapter 3: Meet Boozang
- Proof of Concept Phase
- Pilot Phase
- A Week with Mats
- Pilot Results
- Why Boozang
- Ease of Use
- Focus on Test Automation
- Simple and Solid Language-Based Element Recognition
- Data Management
- Gherkin and BDD Support
- Concurrent Development
- Support and Vision
- Codeless Approach: How Important Is It?
- Chapter 4: The TCS Project
- TCS Organization and Test Automation History
- New Roadmap, New Challenges
- NIS Project Introduction
- Test Automation Stream, NISTA Setup
- Chapter 5: How Boozang Was Born
- Part II: Boozang Main Concepts and Use Cases
- Chapter 6: Starting Up with Boozang
- Creating Your First Project
- Where Are Your Data Stored?
- Using Boozang with the Chrome Extension
- Using Boozang with the HTML Fragment
- Managing Team Access
- Boozang Under the Hood
- Insight from the Trenches
- JIRA Agile Board.
- JIRA Dashboard
- JIRA Structure
- Confluence Pages
- Chapter 7: Main Concepts and Entities
- Modules and Submodules
- Application Environments
- Tests and Test Suites
- Test URL
- Environment URL
- Test Actions
- Keep It Modular, Avoid Monolithic Tests
- Test Suites
- Features and Scenarios
- Searching and Bookmarks
- Recording
- Generate and Reference Test
- Execution and Reporting
- Execution Modes
- Execution Reports
- Projects Settings and UI Customization
- Content Policy
- Integration
- UI Customizations
- Updates from the Trenches
- Chapter 8: Elements Location Approach
- Boozang Location Strategy
- Fine Tuning the Locators
- Locators with Dynamic Tables and Non-unique Elements
- Use Case 1
- Use Case 2
- Use Case 3
- Validating the Expected Results
- Exist
- Validate not exist
- innerText
- Script: JS-Validate
- Is Checked
- Chapter 9: Exit Conditions, Conditional Flows, and Timers
- Exit Conditions
- Conditional Flows
- PCAS Logic Part 1
- Products and Dependent Products
- If-Then-Else Groups
- Loop Groups
- PCAS Logic Part 2
- Checking Financial Data Tables with Loops
- Timers
- Chapter 10: Data Management
- Data Management Concepts
- Test Parameters
- Automapping Parameters
- Project Data (project)
- Module Data (module)
- Test Data (test)
- Loops (loop, group, action)
- Wrapping Up
- Examples from the Trenches
- Chapter 11: Reporting and Troubleshooting
- Test Reports
- IDE Real-Time Reports
- Reports Menu
- Trend Reports
- Troubleshooting Failures
- Root Cause Analysis
- RCA Report
- Part III: Integrations and Advanced Topics
- Chapter 12: APIs and Mixed API/GUI Testing
- Restful APIs
- Why Boozang for Testing APIs?
- API Tests in Boozang
- Setting Up a Simple Test with the Google APIs
- Parsing and Validating the Response
- Server Side Mock with JSON Server.
- API Tests from the Trenches
- API Test Examples
- Mixed API/GUI Scenarios
- Chapter 13: Gherkin and Behavior Driven Development
- Behavior Driven Development
- Applying BDD for COTS Integration Projects
- Gherkin Without BDD: Pros and Cons
- Gherkin Language: Readability Above All, If Possible
- Scenario Readability
- Some Good and Bad Examples
- Example 1
- Example 2
- Example 3
- Chapter 14: JIRA with Boozang via XRay
- Using JIRA with XRay
- Xray for Test Automation
- Boozang Integration with XRay
- Importing Features Files
- Pushing Test Results Back to XRay
- Chapter 15: Jenkins and the Boozang Runner
- Continuous Delivery and the Need for Automating Acceptance Tests
- Puppeteer and the Boozang Runner
- How to Use the Docker Runner
- Keeping Execution Time Low with Parallel Runs
- Parallel Execution and Workers Setup
- Boozang Workers Concepts
- Boozang Workers Setup in the Jenkins Pipeline
- Launching the Workers
- Launching the Master
- Reports and Log Files
- Execution Reports
- Log Files and the Log Formatter
- Root Cause Analysis Report
- Publishing Reports on Jenkins and JIRA
- Cucumber Reports
- HTML Reports
- JIRA Reports
- Complete Working Pipeline
- Test Users Setup
- Set Variables
- Define Job Parameters
- Set Build Information
- Execute Smoke Tests
- Launch Boozang Workers and Master
- Aggregate JSON Reports and Log Files
- Download and Execute RCA Script
- Publish Cucumber Reports
- Get Currently Deployed Version
- Import Results into XRay
- HTML Publisher
- Docker in Docker Setup
- Chapter 16: Boozang for Teams
- Team Collaboration
- Explicit Lock
- Concurrent Development and Safe Refactoring with Branches
- Working with Branches
- Using a Feature Branch Approach
- Branch Naming Convention
- Adding a Develop Branch
- Merging Process
- Tests Map
- Quality Control.
- Warnings
- Missing Plug Test Case
- Un-referenced Test Cases
- Non-unique Element Selectors
- Empty Input Values
- Launch Page Issue
- Errors
- Missing Plug Test Case Target
- Data Error
- Missing Expectation Setting
- Missing Element in Action
- Our Main Learnings
- Conclusions
- Appendix: ROI Example for a Test Automation Initiative
- Index.
