{"title":"子域(分区)测试","authors":"D. Hamlet","doi":"10.1081/E-ESE-120044507","DOIUrl":null,"url":null,"abstract":"In subdomain testing, the input space of the program being tested is divided using a criterion of ‘sameness,’ grouping input points such that it seems unnecessary to try many in the same group. These subdomains are then sampled: it is required that each be covered by at least one test. There are a number of pitfalls in this procedure because the points in a subdomain are never truly ‘the same’; nevertheless, the method is the only imaginable way to systematize testing. Key terms: test coverage, functional testing, structural testing, input partition, sampling, subdomain homogeneity","PeriodicalId":386020,"journal":{"name":"Encyclopedia of Software Engineering","volume":"251 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2010-11-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Subdomain (Partition) Testing\",\"authors\":\"D. Hamlet\",\"doi\":\"10.1081/E-ESE-120044507\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In subdomain testing, the input space of the program being tested is divided using a criterion of ‘sameness,’ grouping input points such that it seems unnecessary to try many in the same group. These subdomains are then sampled: it is required that each be covered by at least one test. There are a number of pitfalls in this procedure because the points in a subdomain are never truly ‘the same’; nevertheless, the method is the only imaginable way to systematize testing. Key terms: test coverage, functional testing, structural testing, input partition, sampling, subdomain homogeneity\",\"PeriodicalId\":386020,\"journal\":{\"name\":\"Encyclopedia of Software Engineering\",\"volume\":\"251 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2010-11-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Encyclopedia of Software Engineering\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1081/E-ESE-120044507\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Encyclopedia of Software Engineering","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1081/E-ESE-120044507","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
In subdomain testing, the input space of the program being tested is divided using a criterion of ‘sameness,’ grouping input points such that it seems unnecessary to try many in the same group. These subdomains are then sampled: it is required that each be covered by at least one test. There are a number of pitfalls in this procedure because the points in a subdomain are never truly ‘the same’; nevertheless, the method is the only imaginable way to systematize testing. Key terms: test coverage, functional testing, structural testing, input partition, sampling, subdomain homogeneity