So here’s my project:
I am building a central interface/dashboard to present the test data for several test types of multiple product versions. We’re using TestNG on our massive product, and while not enough tests are being written, that’s a discussion for another topic. Here’s what the directory structure looks like:
Filesystem/productVersion+testType/uniqueDateAndBuildID/testng-results.xml
That results.xml file contains tags with child test tags, which correspond to a filesystem directory and then xml files containing actual test case results (pass, fail, etc)
The XML parsing and filesystem traversal is all well and good/reliable.
Flow of control:
Client accesses main page –> server opens properties file –> server checks for web server property (either Websphere or Tomcat, if I’m working locally) –> server sets bunch of constants based on that. Constants include: root filesystem directory, filesystem separator (translation), “like types (basically same tests on different platforms)”, and a base URL to append onto. –> server then reads properties file some more and does all of its XML processing. Results are cached in memory as well as to the filesystem using ObjectOutputStream. –> A big list of results is sent back to the client to do the UI processing/display.
Here’s where I run into a problem: I can’t access those Global variables (contained/set in a Globals class…bad I know :-/ ) back on the client, even though they’re in the shared folder. If you’re wondering why I can’t just load the properties again, it’s because the client is GWT-ified Javascript which doesn’t include File(). So my next thought, having done a little bit of upper level Java reading was to maybe use a Globals singleton object and pass that back too..but it seems like that’s just as bad if not impossible. Suggestions here would be great.
This whole thing is pretty tightly coupled, something my previous Java education hadn’t really gotten into yet. And since this is just an internal portal for devs to check, there doesn’t seem to be much of a point in actually testing my code. As long as it displays correctly, logs properly, and handles errors gracefully, right? All in all it’s <15 classes, so it’s not really a big big deal I guess. Should I refactor to clean it all up and make it “better Java”, comment everything to clearly delineate flow of control, or not worry too much about it because it’s small? I know in the future to think more about things before I design them, but I really didn’t know a large amount of the higher Java principles I’ve been exposed to since starting.
edit after doing a bit of thinking, came up with a possible workaround. What about, instead of passing back only a list of results, I passed back some other custom list implementation that included a globals ‘header’ object? I could preserve state.
You could pass those Global variables using a simple object with a HashMap thought a GWT-RPC call or just include this Hashmap with the result you already retrieve in the first place (along the “big list of results [that] is sent back to the client to do the UI processing/display.”)