Knowledge (XXG)

Test suite

Source 📝

25: 137:
that are intended to be used to test a software program to show that it has some specified set of behaviors. A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing. A group of test cases may
203:
might consist of a list of numbers and their primality (prime or composite), along with a testing subroutine. The testing subroutine would supply each number in the list to the primality tester, and verify that the result of each test is correct.
188:(SUT) because abstract test cases remain at a high abstraction level and lack concrete details about the SUT and its environment. An executable test suite must work on a sufficiently detailed level to correctly communicate with the SUT and a 184:, which are derived from abstract test suites by providing the concrete, lower-level details needed to execute this suite by a program. An abstract test suite cannot be directly used on the actual 165:
or a test suite for some specific functionality in the system. It may also contain all tests and signify if a test should be used as a smoke test or for some specific functionality.
161:
Occasionally, test suites are used to group similar test cases together. A system might have a smoke test suite that consists only of
264: 108: 46: 89: 61: 42: 68: 35: 307: 162: 291:, Proc. International Workshop on Testing of Communicating Systems (IWTCS'98), Tomsk, Russia, September 1998. 75: 289:"An Industrial Experiment in Automatic Generation of Executable Test Suites for a Cache Coherency Protocol" 288: 57: 249:
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
122: 169: 270: 260: 185: 177: 252: 218: 82: 176:, which are collections of abstract test cases derived from a high-level model of the 301: 244: 213: 150: 274: 189: 138:
also contain prerequisite states or steps and descriptions of the following tests.
146: 24: 200: 256: 223: 196: 142: 134: 243:
Pinto, Leandro Sales; Sinha, Saurabh; Orso, Alessandro (11 November 2012).
192:
is usually present to interface the executable test suite with the SUT.
18: 245:"Understanding myths and realities of test-suite evolution" 251:. Association for Computing Machinery. pp. 1–11. 49:. Unsourced material may be challenged and removed. 287:Hakim Kahlouche, César Viho, and Massimo Zendri, 141:Collections of test cases are sometimes termed a 8: 109:Learn how and when to remove this message 235: 7: 47:adding citations to reliable sources 14: 23: 34:needs additional citations for 1: 172:, one distinguishes between 16:Collection of software tests 129:, less commonly known as a 324: 257:10.1145/2393596.2393634 182:executable test suites 133:, is a collection of 174:abstract test suites 123:software development 43:improve this article 195:A test suite for a 170:model-based testing 186:system under test 178:system under test 119: 118: 111: 93: 315: 308:Software testing 292: 285: 279: 278: 240: 219:Software testing 131:validation suite 114: 107: 103: 100: 94: 92: 51: 27: 19: 323: 322: 318: 317: 316: 314: 313: 312: 298: 297: 296: 295: 286: 282: 267: 242: 241: 237: 232: 210: 159: 115: 104: 98: 95: 52: 50: 40: 28: 17: 12: 11: 5: 321: 319: 311: 310: 300: 299: 294: 293: 280: 265: 234: 233: 231: 228: 227: 226: 221: 216: 209: 206: 158: 155: 117: 116: 31: 29: 22: 15: 13: 10: 9: 6: 4: 3: 2: 320: 309: 306: 305: 303: 290: 284: 281: 276: 272: 268: 266:9781450316149 262: 258: 254: 250: 246: 239: 236: 229: 225: 222: 220: 217: 215: 214:Scenario test 212: 211: 207: 205: 202: 198: 193: 191: 187: 183: 179: 175: 171: 166: 164: 156: 154: 152: 151:test scenario 148: 144: 139: 136: 132: 128: 124: 113: 110: 102: 91: 88: 84: 81: 77: 74: 70: 67: 63: 60: –  59: 55: 54:Find sources: 48: 44: 38: 37: 32:This article 30: 26: 21: 20: 283: 248: 238: 194: 190:test harness 181: 173: 167: 160: 149:, or even a 140: 130: 126: 120: 105: 96: 86: 79: 72: 65: 58:"Test suite" 53: 41:Please help 36:verification 33: 163:smoke tests 147:test script 230:References 201:subroutine 135:test cases 127:test suite 99:March 2022 69:newspapers 224:Test case 197:primality 143:test plan 302:Category 208:See also 199:testing 275:9072512 83:scholar 273:  263:  180:, and 85:  78:  71:  64:  56:  271:S2CID 157:Types 90:JSTOR 76:books 261:ISBN 145:, a 125:, a 62:news 253:doi 168:In 121:In 45:by 304:: 269:. 259:. 247:. 153:. 277:. 255:: 112:) 106:( 101:) 97:( 87:· 80:· 73:· 66:· 39:.

Index


verification
improve this article
adding citations to reliable sources
"Test suite"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
software development
test cases
test plan
test script
test scenario
smoke tests
model-based testing
system under test
system under test
test harness
primality
subroutine
Scenario test
Software testing
Test case
"Understanding myths and realities of test-suite evolution"
doi
10.1145/2393596.2393634
ISBN

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.