This assignment requires developing a set of test cases that could be used to check the file search tab in eclipse.

Part 1:

Using a category-partition approach like we used in class, list a set of concrete test cases for the tab. You should break the test cases into 3 groups: level 1 (should be run every time to make sure the search is fundamentally working), level 2 (run sporadically to test that nothing has broken over time) and level 3 (tests that should be run only when significant work is done to the search panel).

The easiest way to format your results is in a table.

You should have a column for each category (such as Case Sensitive) and a row for each test. I would also suggest adding a column for test level, but you could make three tables instead.

Your table will end up looking something like (but with much more data in it)

Test Level	Case Sensitive	Files
1	True	*.java
2	False	*.java

You do not want to fully build every combination, but try to find a good set of tests, dropping ones that are unlikely to show you much. A good answer will be something in the 150-200 tests range, with the largest chunk being level 3 and the smallest chunk being level 1.

Part 2:

a) Given your tests for file search, look briefly at each of the other search panels (task search, git search, and Java search). Estimate how many total tests would be required to reasonably test each of these search panels, including a sentence or so to indicate why you think a particular search will require more (or fewer) tests than the file search requires.

b) Look through all the Properties (Preferences on a mac) panels for eclipse. Estimate roughly how many tests would be required to test all of these panels. Use a few sentences to explain why you think that estimate is in the right ballpark.