question

Thanks for the replies.

I'll preface this with the fact that I am pretty new to js. and in early development (but I have already managed to break other's work with insufficiently tested cloudscript).

My experience developing to date is that cloudscript creation is slow, error-prone and stone-age in debugging techniques. I'd appreciate more time efficiency, so I'm eagerly looking forward to the better options that you mention Paul.

I think a viable test strategy would be better with both offline and online testing.

I have some helper code independent of API calls and yet more that only has lightweight API dependency, that should be mockable with minimal effort. I could duplicate my cloudscript in a local environment to test the above functionality. I'm making the assumption that production cloudscript uses node.js, so using a common node stack including tools like Mocha, Sinon JS and Rewire might make sense. Even if my uploaded code is semantically correct, the debug activity loop is time consuming for typos or minor logic mistakes, and a unit test strategy could improve my productivity.

I also had the idea of a helper test title. I guess it wasn't as out there as I initially thought for online testing. These would be more integration than unit tests and would rely on a C# test framework to create calls into the system from a standalone program.

So I spent a while getting half of this strategy working. I used the straight C# PlayFab API to work in the most recent .NET and NUnit (rather than UUnit because my game uses Unity) to build a integration testing framework. It targets a duplicate test title with data copied over from the main title. It works nicely and has helped me pick up some script and economy data errors already.

Duplicating the economy data required writing a special application because I ran into a Catch 22 situation importing bundles and containers because their drop tables required the items, but their items required the drop tables. :-s

Now I'm starting on the pure js unit testing, but I'm blocked and not sure what is going on. I would like to use exactly the same script as I upload to the server. To do this I was planning on exporting functions that I would import into my tests using require. But when I try to use exports or module.exports the upload process complains that they are not defined and will not upload the file. Are module and exports explicity disabled in cloudscript? Or am I missing something else?

Yes, we're aware of the issue with duplicating titles (the chicken-and-egg with items, bundles/containers, and drop tables), and we'll be providing a tool later this year to make that process easier.

For Cloud Script, we're using a V8 JavaScript implementation, and I'm afraid we can't support modules just yet, though that is something we've got on our backlog for investigation.