Code Structure Organization

After you check out the source from the repository, you will find the code to be organized in the following folder structure:

The directory structure has not been updated for a while now. there are new projects that have been added which needs to appear here.
----browser_patrol
----core
----docs
----dom_xchange
----etc
----lib
----licenses
----log
----object_depot
----packages
----resources
----temp
----templates
----test_definition
----testdata
----tray_application
----ui
----website
----wet_common_controls
----wet_meta

The information contained within each folder is as follows:

  • wet_common_controls - C# Common user controls that other projects of WET may need to reuse.
  • wet_meta - C# project for handling some of the configuration / meta data application resources, etc.,
  • browser_patrol - This is a C# class library that contains the implemtation of various forms of representing the actual browser - Browser Treeview, Simulated browser forms
  • dom_xchange - This contains the C# project for xchanging dom information between ruby layer and c# layer.
  • object_depot - Project and associated files of the object depot manager (aka repository manager)
  • test_definition - C# Project to manage the test definition / associated forms
  • tray_application - C# Project for the WET RPC Tray Manager tray application
  • ui - C# project for the main WET UI application. This Project infact calls classes from most of the other projects.
  • core - The WET Core layer (ruby)
  • docs - Name says it all
  • etc - The common data files like configuration file, object identification file, etc .,
  • lib - 3rd party libraries that WET users
  • licenses - Name says it all
  • log - Name says it all
  • packages - Source packages of other opensource tools / frameworks that WET uses
  • resources - images, etc., required by WET
  • temp - A temporary directory
  • templates - Contains the default template for various artificats like test definition etc.,
  • testdata - Data used for testing.
  • website - (Internal use only )

The above organization structure was created to separate out the various components into separate projects. This helps in better reuse.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.