techlist.io
KR EN

quality-assurance

16 posts

toss

Toss Income QA Platform: The Beginning (opens in new tab)

Toss's QA team developed an internal "QA Platform" to solve the high barrier to entry associated with using Swagger for manual testing and data setup. By transforming complex, multi-step API calls into a simple, button-based GUI, the team successfully empowered non-QA members to perform self-verification. This shift effectively moved quality assurance from a final-stage bottleneck to a continuous, integrated part of the development process, significantly increasing product delivery speed. ### Lowering the Barrier to Test APIs * Existing Swagger documentation was functionally complete but difficult for developers or planners to use due to the need for manual JSON editing and sequential API execution. * The QA Platform does not create new APIs; instead, it provides a GUI layer over existing Swagger Test APIs to make them accessible without technical documentation. * The system offers two distinct interfaces: "Normal Mode" for simplified, one-click testing and "Swagger Mode" for granular control over request bodies and parameters. ### From Manual Clicks to Automation and Management * Phase 1 focused on visual accessibility, allowing users to trigger complex data states via buttons rather than manual API orchestration. * Phase 2 integrates existing automation scripts into the platform, removing the need for local environment setups and allowing anyone to execute automated test suites. * The final phase aims to transition into a comprehensive Test Management System (TMS) tailored to the team's specific workflow, reducing reliance on third-party external tools. ### Redefining Quality as a Design Choice * By reducing the time and mental effort required to run a test, verification became a frequent, daily habit for the entire product team rather than a chore for the QA department. * Lowering the "cost" of testing replaced guesswork with data-driven confidence, allowing the team to move faster during development. * This initiative reflects a philosophical shift where quality is no longer viewed as a final checklist item but as a core structural element designed into the development lifecycle. The primary takeaway for engineering teams is that the speed of a product is often limited by the friction of its testing process. By building internal tools that democratize testing capabilities—making them available to anyone regardless of their technical role—organizations can eliminate verification delays and foster a culture where quality is a shared responsibility.

quality-assurancetest-automationswaggerapi-testing+3
discord

Discord Patch Notes: December 8, 2025 (opens in new tab)

Discord has introduced its "Patch Notes" series to document ongoing improvements in performance, reliability, and general system responsiveness. The initiative emphasizes a transparent development cycle where community feedback directly informs engineering priorities and bug-squishing efforts. **User-Driven Bug Tracking** * Engineers actively monitor a Bimonthly Bug Megathread on the community-managed r/DiscordApp subreddit. * This collaborative approach allows the development team to identify and address user-reported friction points that may not be caught during internal testing. **Beta Testing via TestFlight** * iOS users can opt into a TestFlight version of the application to test upcoming features and early builds before they are released to the general public. * This program serves as a critical frontline for identifying edge-case bugs and ensuring stability across the mobile ecosystem. **Deployment and Rollout Procedures** * All documented fixes in the series have been officially committed and merged into the codebase. * Changes are distributed through a rolling deployment, which means updates may arrive on individual platforms at different times depending on the release schedule. To ensure the best user experience and contribute to the platform's stability, users are encouraged to participate in the TestFlight program or report specific technical issues through the designated community channels.

quality-assurancesoftware-engineeringperformance-optimizationmobile-development+3
toss

Working as a QA in a (opens in new tab)

Toss Place implements a dual-role QA structure where managers are embedded directly within product Silos from the initial planning stages to final deployment. This shift moves QA from a final-stage bottleneck to a proactive partner that enhances delivery speed and stability through deep historical context and early risk mitigation. Consequently, the organization has transitioned to a culture where quality is viewed as a shared team responsibility rather than a siloed functional task. ### Integrating QA into Product Silos * QA managers belong to both a central functional team and specific product units (Silos) to ensure they are involved in the entire product lifecycle. * Participation begins at the OKR design phase, allowing QA to align testing strategies with specific product intentions and business goals. * Early involvement enables accurate risk assessment and scope estimation, preventing the "shallow testing" that often occurs when QA only sees the final product. ### Optimizing Spec Reviews and Sanity Testing * The team introduced a structured flow consisting of Spec Reviews followed by Q&A sessions to reduce repetitive discussions and information gaps. * All specification changes are centralized in shared design tools (such as Deus) or messenger threads to ensure transparency across all roles. * "Sanity Test" criteria were established where developers and QA agree on "Happy Case" validations and minimum spec requirements before development begins, ensuring everyone starts from the same baseline. ### Collaborative Live Monitoring * Post-release checklists were developed to involve the entire Silo in live monitoring, overcoming the limitations of having a single QA manager per unit. * This collaborative approach encourages non-technical roles to interact with the live product, reinforcing the culture that quality is a collective team responsibility. ### Streamlining Issue Tracking and Communication * The team implemented a "Send to Notion" workflow to instantly capture messenger-based feedback and ideas into a structured, prioritized backlog. * To reduce communication fragmentation, they transitioned from Jira to integrated Messenger Lists and Canvases, which allowed for centralized discussions and faster issue resolution. * Backlogs are prioritized based on user experience impact and release urgency, ensuring that critical bugs are addressed while minor improvements are tracked for future cycles. The success of these initiatives demonstrates that QA effectiveness is driven by integration and autonomy rather than rigid adherence to specific tools. To achieve both high velocity and high quality, organizations should empower QA professionals to act as product peers who can flexibly adapt their processes to the unique needs and data-driven goals of their specific product teams.

quality-assurancedatabase-designjiraperformance-monitoring+4
discord

Discord Patch Notes: May 1, 2025 (opens in new tab)

Discord’s Patch Notes series serves as a transparent log of the platform's continuous improvements in performance, reliability, and general usability. By combining developer-led bug squishing with direct community feedback, the team aims to deliver a more stable experience across all supported platforms. ### Community-Driven Bug Tracking - Discord leverages the community-run r/DiscordApp subreddit to host a Bimonthly Bug Megathread. - This channel allows users to report specific issues directly to the Engineering team, ensuring that user-facing bugs are identified and prioritized for future sprints. ### Early Access and Beta Testing - iOS users have the option to join Discord’s TestFlight program to test upcoming features before they reach the general public. - This experimental environment allows power users to help "squish" bugs in a live mobile context, providing the engineering team with critical data before a global release. ### Commit and Rollout Procedures - The series clarifies that all listed fixes are officially committed and merged into the codebase. - Because Discord uses a staged rollout system, these changes may take time to propagate to individual platforms and users even after the notes are published. Users looking to contribute to the platform's stability should utilize the dedicated Reddit megathread for bug reporting or join the TestFlight program to provide early feedback on upcoming mobile builds.

quality-assuranceperformance-optimizationmobile-developmentios+3