Automated Testing

[nathggns]

We really need to add automated testing to this library before we can release the RC.

The issue we have is a lot of the code in this library can't be easily unit tested, as it is heavy UI code. There are a few classes that can be easily unit tested, which are the following

• [x] DDTPoint
• [x] DDTCSS

Parts of the following classes can easily be united tested, whereas others cannot

• [ ] DDTElement
  • [x] getNode
  • [x] offsetTop
  • [x] show
  • [x] hide
  • [ ] calculateBounds (Maybe?)
  • [x] getLeftPaddingAndBorder
  • [x] getParentWithSelector
  • [x] getVerticalBorders

This leaves the following classes and methods that cannot be easily unit tested and we will therefore have to find another way.

• [ ] DDTElement
  • [ ] swap
  • [ ] clone
  • [ ] getUniqueStyles
  • [ ] cloneStyles
  • [ ] cloneUniqueStyles
  • [ ] cloneAttributes
  • [ ] getInheritedBackgroundColor
• [ ] DDTPositionableElement
• [ ] DDTTable
• [ ] DDTShadowTable

The following classes do not need to be unit tested as they don't have any extra functionality (but can't be removed for various reasons)

• DDTRow
• DDTShadowRow

[nathggns]

As for a CI, I believe that from personal experience, Travis CI is the best free CI for open source projects, and it has great github integration. However, if we want to use this before we make the repo public I think you have to pay or use the self-hosted version (I can't remember specifically).

What do you think @MrRio?

[nathggns]

I'm not sure what the best solution would be for testing the classes that cannot be unit tested yet. Will need to look into that a bit more.

@MrRio

[nathggns]

I think we should use the karma test runner as it helps you to run your tests across all browsers, which will help with #35.

[MrRio]

There must be some way of mimicking these events. Yeah karma looks good, maybe look at getting it up on Travis CI too.

[nathggns]

Going to move the rest of this to post release.