nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Unit testing server side javascript

akoudrin

I'm about to start development on Alfresco 4.2.c using the existing Maven setup. I anticipate mostly working with Share. Furthermore, I anticipate most of development to be on javascript, both server and client side.

I'm currently looking at unit testing javascript. On client side, I've found Jasmine running PhantomJS to be good. However, I'm struggling to find and setup javascript unit testing for server side. At the moment it looks like doing a more of an end-to-end integration tests is the only feasible solution.

How has Alfresco Share done this kind of unit testing? What would you suggest a developer of new features, like me, does?

Find more posts tagged with

Comments

zladuric

For what it's worth, the furthest that I've got to is, I've built tests for my RESTful backend interfaces - just calling the POST/PUT/GET/DELETE/GET on my scripts and checking if everything is working as expected. I don't see how unit testing could be implemented, but please post back here if you find a way.

akoudrin

Yes, that's one of the possibilities for integration testing. What we really want, with so much server side javascript, is to have lots of unit tests to cover our code close to 100%.

zladuric

Hmm. I usually wrap everything in the controller in at least a "main" method. You could, perhaps, separate most of the controller code to a *.lib.js file, define some of your own global vars and include the lib.js file in a test version?

So your testController.js file looks like this (and you call it via that command servlet, not as a web script).
<javascript><import resource="classpath:ctrl.lib.js">
var companyhome = "fakecompanyhomeobject"
var document = fakedocument;
var args = { site: "fakeSite", nodeRef: "fakeNodeRef"};
main();
</javascript>

And your regular controller just holds the import statement and main().

Now that I've written it, it sounds kind of clumsy, but at least it's a start, right?

akoudrin

Ideally I'd like to find a framework to streamline writing lots of tests. Similar to Jasmine/PhantomJS framework.

zladuric

Let us know when you do

zladuric

Hmm, can you find something useful here?
http://www.springsurf.org/sites/1.0.0.CI-SNAPSHOT/testapidocs/org/springframework/extensions/webscripts/package-tree.html

Alfresco webscripts are done on springframework webscripts package.

akoudrin

So do Alfresco Share developers look at this forum? Rather than trying to guess I'd actually like to get their answer to this. Or perhaps some could point me to the more appropriate forum?

ddraper

I'm probably one of the very few Share developers to actually look at the Spring Surf forums, and I mostly just respond telling them to directly questions to the Alfresco forum. The honest answer is that up until now we haven't done a great deal of automated unit testing on Alfresco Share. There is an automated FVT suite within Surf that is based around TestNG but that is just for testing the basic Surf functionality. We are now starting to make a more concerted effort to automate the testing of Share but that does not really involve JavaScript unit tests but rather a more functional test approach. We do have Dojo DOH based unit testing on the new widget suite that we are developing though.

akoudrin

Great. Thank you for that honest answer. That's what I gathered in my preliminary web research too. I'll probably stick to our functional end-to-end test idea.