Bridging Manual and Automated Testing: InfoWatch Engineer Outlines Unified Quality Process
InfoWatch senior test engineer Mikhail Shalepo has shared a comprehensive internal regulation that connects manual and automated testing into one coherent quality process. The article uses the metaphor of an “orange” to describe the overlapping area of functional verification where the two testing approaches must deliver a single, reliable signal about product state.
Shalepo notes that when automation volume, environments, and mandatory runs remain small, teams often rely on shared context. As the product grows, this implicit understanding disappears, creating the need for explicit rules on selecting automation candidates, validating new tests, defining mandatory regression sets, classifying failures, and recording manual compensation.
Core Principles of the Regulation
The document distinguishes between process rules—who decides, what result is recorded, and who owns the next step—and specific engineering decisions for individual features. It establishes that manual testers review the purpose of an automated scenario rather than its code, and that every failure must receive an owner and follow-up action before a run is considered resolved.
The regulation is split into two blocks: development and verification of new functionality, and full regression testing before release. Both blocks follow the same three-stage structure—preparation, execution, and completion—producing clear artifacts at each step.
Feature Development Block
Before a sprint, manual testers and automation engineers meet to discuss scenarios worth automating. Decisions are turned into backlog tasks instead of remaining informal promises. During the sprint, the manual testing team acts as the customer of automation meaning, while smoke tests must pass before any build reaches manual verification. At sprint end, coverage status is recorded directly in TMS Scale to keep the single source of truth up to date.
Pre-Release Regression Block
Before regression begins, teams align on the full scope of checks, supported configurations, and exit criteria. During execution, automated results are triaged jointly with developers; every failure is classified, assigned an owner, and linked to a task or defect. Manual compensation is documented only when an automated signal cannot be restored quickly. At the end of regression, the team produces a connected set of artifacts that allow full reconstruction of the release decision without relying on chat history.
Shalepo emphasizes that the regulation does not guarantee zero defects or automatically shorten regression time. Its value lies in making the basis for release decisions observable and repeatable across the team.
Related articles
Rostelecom Outage Triggers 29-Minute Mass Disruptions Across Russian Internet Services
A 29-minute failure in Rostelecom's data transmission network on August 6 caused widespread access problems to Russian online services. The operator quickly rerouted traffic to backup equipment, restoring normal operations without revealing the root cause. Users reported issues connecting to marketplaces, banks, social platforms, IT company services and other telecom providers. The majority of complaints originated from Rostelecom's own subscribers who experienced connection and service access failures. Although the incident remained brief and did not escalate into prolonged digital disruption, it highlighted the heavy reliance on a single major provider. The event demonstrated how even a short technical problem at a large operator can simultaneously affect access to stores, financial services and everyday online platforms.
Read-Only Utility Automates Detailed Audits of UserGate NGFW Firewall Policies
A cybersecurity specialist at Gazprom CPS developed a read-only utility to analyze large-scale UserGate NGFW firewall policies without making any configuration changes. The tool connects via the UserGate XML-RPC API to collect rules, statistics, zones, network lists, services, users, and groups, then normalizes the data into a unified model for analysis. It performs eleven independent checks grouped into lifecycle, overly permissive access, observability, and documentation categories, flagging rules that have not fired recently, allow management ports broadly, lack logging, or have empty descriptions. Results are exported to a navigable Excel report featuring a rules-by-checks matrix, human-readable object names, and editable manual verdicts such as OK, requires attention, or false positive. The first full run on a production policy with over 1000 rules and 4500 related objects took 24 minutes and highlighted 39 percent of rules for review, with more than half showing multiple red flags. The approach preserves the original snapshot in JSON for repeatable offline analysis and comparison over time.
Internet Outages Disrupt Access to Russian Websites and Applications Across Multiple Regions
Users in several Russian regions reported widespread connectivity problems where internet access appeared available but failed to load most domestic websites and online services. Affected areas include Saint Petersburg along with Nizhny Novgorod, Rostov, and Tyumen regions according to reports compiled by the Telegram channel Baza. Connections remained technically active yet produced repeated errors when attempting to reach Russian sites, mobile applications, and web-based platforms. The precise scale of the disruption remains undetermined and it is unclear whether the incidents stem from a single technical fault or simultaneous failures among multiple network operators. No official statements have been issued regarding the root causes or expected restoration timelines. Individuals affected continue to refresh pages and restart applications while waiting for services to recover.
Step-Up Authentication vs 2FA: Implementing Additional Verification for Sensitive Operations in Corporate Systems
Traditional two-factor authentication secures only the initial login, leaving active sessions vulnerable to misuse during sensitive tasks such as accessing payroll data. Step-Up Authentication addresses this by requiring extra verification at the moment of critical actions rather than at login. The article details how one project moved beyond standard Identity Provider features in WSO2 by building a dedicated PIN-code service and gateway-2fa microservice. This approach uses signed cookies with TTL controls and JWT cross-checks to enforce elevated trust levels without disrupting normal user flows. The solution aligns with Zero Trust principles and was monitored via Matomo and ELK for usage and performance metrics. Key implementation considerations include balancing TTL duration, encrypting stored PINs, and conducting load testing before deployment.