VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesNotesMethod
Search occupations, majors…
EN
  • English
  • 简体中文
  • 日本語
  • Español
  • Português
  • Français
VLO
VOLO

Understanding how automation changes work — task by task, with the evidence shown and the uncertainty admitted.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodWill AI replace my job?AboutRole diagnosisOpen dataOntologyVOLO ProPrivacyTerms
© 2026 VOLO
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisFirst AI experimentVOLO ProMethod & evidenceAboutFollow an occupationSearch
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterContent moderatorCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerTax preparer / tax agentVoice actorMedical coderData analystInsurance claims handlerTechnical writer / documentation engineerJunior software developerInsurance underwriterHR / recruiterLoan officer / credit officerFinancial analystProcurement / supply chain specialistJournalistSales / account managerReal estate agentIT support specialist / helpdeskAuditorManagement consultantBackend developerAI researcherProduct / UX designerBusiness systems ownerE-commerce operations specialistActuaryRadiologistData engineerProject managerLawyerMedical assistant / clinic assistantQuantity surveyorMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Financial adviser / financial plannerCompliance officerLibrarianArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantCivil / structural engineerSecurity guardBus driverInsurance agentSchool teacherGeneral practitioner / primary care doctorAirline pilotWaiter / restaurant serverRadiographer / radiologic technologistAuto mechanic / vehicle technicianPolice officerSonographerAir traffic controllerVeterinarianPhysiotherapist / rehabilitation therapistDentistConstruction workerSocial workerRegistered nurseCare worker / nursing assistantPlumberAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorMetro train driverReceptionist / front desk
Robotics
Retail cashier / shop assistantContainer port workerWarehouse workerAssembly line workerMedical laboratory technicianWelderChef / cookCleaner / janitorFarmerFirefighterCabin crewElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinanceLawVisual communication designMarketingNursingBusiness administrationEducation and teacher trainingArchitecturePublic administrationMedicineHospitality and tourism managementEconomicsInformation systems
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›Software tester / QA engineer›2025-12-31
DeploymentCognitive automation2025-12-31

In a nine-month production deployment at ByteDance, an LLM tool generated 3,196 API regression test cases, and 85.4% of its code was adopted

Software tester / QA engineeroccupation page →
Event date / reported
2025-12-31 · reported 2026-07-27
Evidence stage
DeploymentAn employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Tasks this bears on
Writing test cases and automation
Turning requirements into cases, and cases into scripts that run in the pipeline.
Automating✓ Evidence-backed
Where this applies
A peer-reviewed experience paper by university and ByteDance authors about a tool deployed at a large consumer internet company. It says API regression tests for cross-service business flows are still largely built and maintained by QA engineers, and that in a nine-month production deployment starting in March 2025 the tool generated 3,196 test cases with an overall code adoption rate of 85.4%. Adoption varied widely by business line; the authors built the tool and measured its adoption themselves.
What this means
A second large company reports machine-drafted regression tests being adopted into its codebase at scale, starting from work its own paper says QA engineers still did by hand. Drafting the cases is shifting to the tool; the engineers review and keep them.
What it does not yet show
One company's tool measured by its builders; it does not show fewer QA engineers.
What you can check
Open arXiv:2607.24000 and find "In a 9-month production deployment starting in March 2025, NL2Test generated 3,196 test cases".
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rest on evidence instead of inference.
Source
You, Dong, Wang, Li, Peng (Fudan University and ByteDance) — "Industrial Practice of LLM-Based Test Case Carving and Assertion Generation (Experience Paper)", arXiv:2607.24000 (27 July 2026; ISSTA 2026) · verified 2026-09-27 · Claude (VOLO agent) · interpreted 2026-09-27 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Software tester / QA engineer →All recent changes →How events become evidence →