How rutbelcarlostc/prueba-automatica works
Project Type and Purpose
• This is a Java-based test-automation framework (Maven project) that exercises a web application’s invoice creation UI, downloads the resulting PDF, and performs visual assertions on the PDF using Applitools Eyes.
High-Level Components
• Test Runner (Maven Surefire)
• Test Layer (src/test/java)
• Page Object Layer (src/main/java/pages)
• Utility Layer (src/main/java/utils)
• Resource Store (chromedriver, test.properties, sample PDFs, ImageTester JAR)
• WebDriver (ChromeDriver)
• AUT (Application Under Test – the invoice web UI)
• PDF Handling (downloaded invoices + FileUtils)
• Visual Validation Service (Applitools Eyes)
Relationships & Data Flows
a. Maven Surefire invokes Test Classes (PDFTests, InvoiceFlowTests via BaseTests).
b. Test Classes call page objects (LoginPage → SignupPage → InvoiceGeneratorPage → InvoicePreviewPage).
c. Page objects use WebDriver (via ChromeDriver) to manipulate the AUT.
d. On invoice generation, the AUT returns a downloadable PDF.
e. FileUtils (utility layer) reads the PDF from disk.
f. EyesManager sets up Applitools SDK; test sends PDF snapshots or images to Applitools Eyes for visual validation.
g. Applitools Eyes returns pass/fail that the test runner captures.
Architectural Patterns
• Layered POM structure:
• Test layer depends on Page Object layer
• Page Object layer depends on WebDriver and AUT
• Utility layer is shared across pages/tests
• External-service integration: Applitools cloud service for visual testing
• Configuration abstraction via test.properties
Key Points
• Major directories as logical modules.
• Configuration flow: test.properties → BaseTests → EyesManager.
• Call out the ImageTester_3.7.1_Linux.jar if it’s used for converting PDF pages to images.