[Sugar-devel] Regarding the splitting of bus.js into its own repository.

[Daniel Narvaez]

On 18 May 2013 09:21, Aneesh Dogra <lionaneesh at gmail.com> wrote:

> Hello,
>
>
Hey!


> I was wondering on how would we preserve the history of sugar-html-core
> repository?
>

See below.


> *Secondly,* I guess the only thing I need to do is to make another
> repository add bus.js to it and edit other files in sugar-html-template,
> sugar-html-core and sugar-build according to that change. Is there anything
> else I need to do?
>
>
Pretty much. Make two clones of sugar-html-core (to preseve history),
rename each to sugar-html-bus and sugar-html-activity, edit and remove
stuff from them. Update sugar-html-template, try to make an activity from
it and test that activity closing still works. Update sugar-build to pull
the new repos.



> *Third: Regarding the test framework.* Do we use Jasmine to write tests?
> If yes, how do we test socket communications?
>

At the moment we are using jasmine and karma as a runner. Manuel is still
researching so it might change. Though I tend to think it's fine to start
developing some bits on jasmine/karma (ccing Manuel to get his opinion
about this too), it will help us to make a more informed decision and I
suspect whatever we choose it won't be hugely different, so adapting will
not be a lot of work.

To be able to test the bus, we need to setup the runner to run stuff inside
sugar. I posted some details about it in other threads. I can probably do
that for you after I got the build under control again. Or you can give it
a try, I guess it make sense to re-discuss after you are done with the
split.

About the tests themself, I think we should start adding a sendMessage
test. In sugar we can add TestAPI to apisocket.py. Maybe just an echo(text)
message. Then in the unit test we can try to send a test.echo("Hello!")
message and verify that we get the expected response.

We will need tests for the streams too, but perhaps that's a second step.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130518/fc6b5a2e/attachment.html>