Urgent.News

What's breaking now, across thousands of outlets.

Tech

Claude tự chạy regression test app Flutter của mình trong lúc mình ngủ

Hồi trước mình làm ở một công ty ví điện tử màu hồng ở Việt Nam. Ở đó anh leader giới thiệu cho mình một tool viết automation test khá hay tên là Maestro. Ảnh chỉ mình cách xài, và đó là lần đầu mình biết code automation test cho mobile app, rồi test e2e trông như thế nào. Phải nói là Maestro làm quá tốt. Cài đặt dễ, inspect element dễ, viết flow cũng đơn giản hơn hẳn mấy công cụ team QC đang…

Claude, a Vietnamese fintech startup, developed an automation testing tool called Maestro. He first learned about the tool while working at a pink-colored fintech company in Vietnam. Maestro made it easy to code automated tests for mobile apps, and Claude found it much simpler to use compared to the team's previous tools. He was impressed by its ease of installation, easy inspection of elements, and simple flow writing.

However, his team did not involve him in the testing process, as they promptly handed over features to quality assurance (QC) for testing. With the rise of AI, Claude joined an outsource company where AI was integrated into every aspect of the coding process, from requirements to implementation. He had to adapt quickly to this fast-paced environment and focused on learning how to write effective prompts for optimal results.

Despite the challenges, Claude decided to create an automation testing suite to replace the heavy regression testing workload typically assigned to QC. With Maestro's available command-line interface (CLI) and machine learning capabilities, he could write a single prompt and let the AI explore the existing test cases, set up flows, and assign missing test IDs.

The goal was to run all test cases in one go and flag any issues for fixes. Although the process was not as fast as he had anticipated, it significantly reduced the burden on QC. Now, when a team member finishes coding a feature, they simply add it to the automation test suite for further regression testing. Claude emphasized that while code quality was still important, the primary focus should be on meeting functional requirements and ensuring overall performance.

He encouraged other app and web developers to try this approach to save time and effort in reviewing their own code.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

When Redis goes down, does your app die?

The Problem: The App Dies There was an incident that caused our application to fail because our Redis cache went down. It was in the middle of moving to a larger compute instance to handle a higher…

  • Redis cache failure significantly impacted application experience
  • Resilient Cache-Aside approach implemented to handle exceptions
  • Circuit Breaker pattern improved app performance and user experience

Using fstab instead of autofs for a samba share

A few weeks ago, I borrowed a Raspberry Pi 4B from a friend. Since it wasn't going to be used for a while, I decided to set up a network storage for our home network.

  • Author used Samba for network storage on Fedora Server 38
  • Initial autofs and crypttab configuration failed due to race condition
  • Fstab permanently mounted drive, solved Samba access issue

More from Sunday 27 September →