Javascript API Test Suite

[Josip Lisec]

Let me just say thanks for your really the fast reply.

On Mon, Mar 29, 2010 at 11:19, Aaron J. Seigo <aseigo at kde.org> wrote:
> that will be one of the important points to figure out for the proposal, in
> fact: what will the app used to run the tests look like? will it be a C++
> application that wraps a Javascript Plasmoid (essentially a simplified version
> of plasmoidviewer that can load and run tests), will it be a Javascript
> Plasmoid itself (while possible, this raises the of using the framework to
> test itself; perhaps not a big problem though)

In my option, implementing it as a JavaScript Plasmoid wouldn't be
that useful for developers, a command-line tool, ie. C++ application
which wraps JavaScript Plasmoid seems like the most logical choice,
thanks for the hint. Later, maybe a Plasmoid which would monitor an
directory containing tests and report the results from command-line
tool in a more user-friendly manner would be a nice addition for
Plasmoid developers.

> the jQuery unit testing framework looks interesting; probably the biggest
> amount of work in re-using that, i imagine, will be to remove the assumption
> that it is running inside an html document. it might be possible to export a
> document object into the QScript environment that bridges to a QWebFrame?

I think that re-using jQuery unit testing framework wouldn't be such a
problem, the only code that depends on browser is the part which
displays results, this could be easily modified to print to stdout.

> using http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/API as a
> guide to what needs to be tested is the way to go to compile such a listing.

What about Plasmoids which ship by default with KDE, are their
developers supposed to write tests after the framework is completed,
or is it part of the task also?

Cheers,
Josip Lisec