René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test Smell: it is not a good test practice to use the loop in the test","articleBody":"Hi!\r\n\r\nWe notice that you use the loop structure in your test cases.\r\nFor example, testQualityScoresIntArray() in FastqToolsTest.java\r\n\u003cimg width=\"497\" alt=\"截屏2022-08-17 下午5 17 26\" src=\"https://user-images.githubusercontent.com/110402847/185083359-94544a0a-e17c-454f-9406-d4fa380e6774.png\"\u003e\r\n\r\nHowever, using the loop in test cases is not a good test practice.\r\nWe analyzed the relevant Stack Overflow posts and summarized four potential negatives it brings:\r\n1. Loops make the test case more complex\r\n2. In most cases, a loop can be replaced with a data-driven test that is more readable.\r\n3. Loops break the assert-for-one-thing thumb rule. I don't mean a single assert statement.\r\n4. When a test fails, knowing the reason is more complicated.\r\n\r\nSolution:\r\nTo avoid using the loop in the test, JUnit provides an annotation (i.e., @ParameteredTest), enabling a test case to run multiple times with different parameters.\r\nWe provide a usage example here:\r\n\u003cimg width=\"622\" alt=\"image\" src=\"https://user-images.githubusercontent.com/110402847/185083811-1d731ae3-0188-475f-b378-714beb492e7a.png\"\u003e\r\n","author":{"url":"https://github.com/TestSmell","@type":"Person","name":"TestSmell"},"datePublished":"2022-08-17T09:23:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/1038/biojava/issues/1038"}