similar line of questioning ^ has anyone attempted...
# suitescript
d
similar line of questioning ^ has anyone attempted to do full end-to-end UI testing (for Suitelets) against an actual NS internal account in their build pipeline? I am wanting to give it a shot with along with Jest/Puppeteer, but idk what kind of nightmare I might be in for... would be good to know some "gotchas"
b
dont do jest
jest is very specific in running on node only
your best chance is something like mocha, or even the older jasmine
those frameworks also target browsers, which more closely matches what SuiteScript offers
expect to strip out functionality related to asynchronous tests
anything related to setTimeout has to go
c
I'd def be interesting in seeing some UI testing just to see how its working
👍 1
b
expect to modify code related to stacktraces
d
@battk seemed Jest is ok for UI/Browser testing with Puppeteer? https://github.com/smooth-code/jest-puppeteer#usage I haven't began to dig into it admittedly, but just on minimal looking into it thus far did not seem to be a "show-stopper" (would prefer to just keep things with Jest since we are already using with the linked NS Unit Test style testing)
b
oh
you wanted to use it with puppeteer
thats essentially means using a headless browser to login to netsuite
d
yes, correct - that was my thought on approach
b
thats way more puppeteer than jest
d
fair, agreed
b
I wouldnt expect it to be something worth doing unless that is a very important suitelet
s
perhaps worth doing if this suitelet is a product (i.e. SuiteApp?)
💯 1