Hi Developers, I need some input on process implem...
# suitescript
s
Hi Developers, I need some input on process implementation. We are a growing team of NetSuite developers, and I’d like to know what measures your teams take to reduce bugs. I know code reviews are common, but what additional processes do you have in place to improve quality? We do code reviews as well, but we still end up missing things. Do you use any AI tools for improving code quality or reviews? Any other ideas or suggestions would be appreciated.
p
I use automated testing and linting to catch issues before code review. Also I run changes through a sandbox test pack so bugs show up before anything goes to production.
d
Use typing (TypeScript), unit tests, linter. github actions, integration tests via Selenium
s
We do the same as Dmitry, but swap out Selenium for Playwright
d
What are Playwright benefits? Maybe I should switch too?
s
For us, it was just lightweight (compared to Selenium). Since playwright is itself written in TypeScript it's familiar. In our case it's got very handy dandy API test capabilities that allow us to simply reuse a developer's existing Netsuite Login session [no additional authentication shenanigans required]. So a developer already logged into netsuite can also run things like RESTlet integration tests via playwright. Perhaps ironically, we haven't used it as much yet for e2e web testing. https://playwright.dev if you want to check it out.
webstorm added playwright support recently, so we also get the nice integrated UI for playwright tests in the IDE
šŸ”„ 1
amazingly, looks like despite its youth, playwright has over twice the github 'stars' than selenium?
šŸ‘ 1
d
Wow, I've tried the playwright and it just worked. No dances with a tambourine like Selenium normally requires šŸ™‚
šŸ‘ 1