{"title":"如何(不)消除测试环境中的技术债务","authors":"Valentin Guerlesquin","doi":"10.1109/TechDebt.2019.00008","DOIUrl":null,"url":null,"abstract":"All software systems, from new developments to legacy systems, suffer from test automation backlogs, i.e., manual tests that stagnate the rate of development and innovation. I argue that such backlogs are really technical debt. I expose here six behavior that may ruin your goal to remove test automation technical debt.","PeriodicalId":197657,"journal":{"name":"2019 IEEE/ACM International Conference on Technical Debt (TechDebt)","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-05-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"How (not ) to Remove Technical Debt in Testing Environments\",\"authors\":\"Valentin Guerlesquin\",\"doi\":\"10.1109/TechDebt.2019.00008\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"All software systems, from new developments to legacy systems, suffer from test automation backlogs, i.e., manual tests that stagnate the rate of development and innovation. I argue that such backlogs are really technical debt. I expose here six behavior that may ruin your goal to remove test automation technical debt.\",\"PeriodicalId\":197657,\"journal\":{\"name\":\"2019 IEEE/ACM International Conference on Technical Debt (TechDebt)\",\"volume\":\"38 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2019-05-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2019 IEEE/ACM International Conference on Technical Debt (TechDebt)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/TechDebt.2019.00008\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2019 IEEE/ACM International Conference on Technical Debt (TechDebt)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/TechDebt.2019.00008","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
How (not ) to Remove Technical Debt in Testing Environments
All software systems, from new developments to legacy systems, suffer from test automation backlogs, i.e., manual tests that stagnate the rate of development and innovation. I argue that such backlogs are really technical debt. I expose here six behavior that may ruin your goal to remove test automation technical debt.