Building a Minimalist UI Test Framework with Playwright and Pytest
Vladislav Timashenkov from InfoWatch shares a streamlined method for building a UI test automation framework. The approach emphasizes direct use of Playwright capabilities rather than wrapping them in custom abstractions.
The framework starts by launching a single Chromium browser process for the entire test session using a session-scoped fixture. Settings such as headless mode and slow motion are stored separately in BROWSER_SETTINGS to allow environment-specific configuration through variables or files.
Authentication is handled without UI interaction. A factory fixture uses the requests library to call the login API endpoint and extracts cookies for later use in browser contexts. This design supports multiple users during a single test run.
Isolated BrowserContext instances provide test separation. A context factory fixture accepts authentication data, applies CONTEXT_SETTINGS including base URL and locale, and ensures all contexts are closed after each test function.
The page fixture combines the authenticated user data with the context factory to deliver a ready-to-use page object. Because the fixture scope is function-level, every test receives a fresh page with pre-applied cookies.
Page Object classes encapsulate business logic only. Locators are exposed as properties that return fresh Locator instances on each access, taking advantage of Playwright’s lazy evaluation and automatic waiting. Methods such as create_tag and delete_tag_by_name perform interactions without additional explicit waits.
A sample test demonstrates creating a tag with generated data from Faker and verifying visibility using the expect assertion API. The article concludes that this minimal infrastructure scales easily as new page objects are added.
Related articles
Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour
A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.
Yandex Tests Compass Device for Taxi Navigation During GPS Outages
Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.
Apple Attributes Widespread Service Outage to Faulty Internal IT Update
Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.
Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay
On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.