DL.3 Notes

[vagosdim]

Deliverable 3: For 28/4 try to have tests and a 1st refactoring of a simple use case (eg Load Project); if time, incrementally add tests and refactorings for other use cases.
Report list of test cases and refactorings in terms of UML diagrams (before/after change).

28/4 [Pvassil]
Try sth like 1st refactoring of "LOAD project" + its tests(not everything);
[if time] incrementally add use cases + tests;
Report list of tests; {before, after} pairs at the design level

[vagosdim]

GlobalDataKeeper

-Almost all data of the tool
-Isolate the method we want to test from the datakeeper -> void setData()

Example1: Test TreeConstruction class => fake DataKeeper => create FakeDataKeeper which extends DataKeeper and overwrites the setData(), method and populates some of the attributes of DataKeeper with simple data instead of parsing real data and stuff.

General idea:

1. Create FakeClass that extends original
2. Create fakeMethod() that overwrites original
3. Create UnitTest

ex. testConstructTree() method

[vagosdim]

More General Tests -> Too much in the Gui!
-Compare what is illustrated in a JTable before and after the change

• Three attributes:

  1. detailedModel
  2. generalModel
  3. zoomModel
     --> dump contents in some text file, then do the changes. To test, compare the file contents of the original table models and compare to the contents of the refactored.

• Gui ==> change the above mentioned attributes to protected instead of private to do the tests. (protected renders attributes accessible within the same package without accessor methods)

• Need to offload the class:
  Options:

  1. subclass the Gui
  2. (the one we want) BuissnessLogicClass to offload code for loading in the Gui ==> acts as a intermediary between DataKeeper and Gui with load methods

• So as not to populate the code much, dump contents to .txt files and do the tests by comparing the contents to the .txt.

• In the Gui there are methods that do some useful process on data --> move the logic to the Data Keeper "Move behavior close to Data" --> Make Data class a "service provider".

Example: constructColumns() @Class TableConstructor

[vagosdim]

14/04 Notes

Do a little refactoring for the tests!!!

• The Server class --> push use cases to the server classes.
• Take code inside action listeners to server class --> need to refactor before testing, tool is not in a consistent state.
  ex. Show FullDetailedLifetime

USE CASES

1. Create new Project
2. Load existing project
3. Zoom in/out
4. Parameter lists