Long question short: Do you think there is knowledge obtained from experience that is not in the docs? For example: Should you hardcode the IDs of the custom fields, or get it from script parameters?

you can change your internal ids for fun if you make a metadata file with all your internal ids

What do you think about the first question?

for example I have an unhealthy fear of server restarts, and a crippling fear of revenue recognition

btw, how do you do the testing?

mocha based tests

will try to push the team culture to do more testing. thanks very much.

you may want to consider jest based tests for netsuite, their sdf team chose it for integration into sdf

great question, short answers is yes. There's a ton you will learn by 'just doing it' that the docs don't cover

@battk When you write tests, you host it on NS, right? let's say you want to test a Restlet that should create a certain record. To check that this record was created you need the code to be on NS, not locally. Otherwise, you will need another Restlet that tells you if the record was created or not. Right?

No, test in node and stub or mock the suitescript api you use

are you referring to this? https://www.npmjs.com/package/@oracle/suitecloud-unit-testing

Again, i do mocha tests, while the suitecloud unit testing uses jest

I still don't understand how do you call Netsuite? Let's consider my example, how would you check if a record has been created or not?

You dont, you create a mock record with fake functions

I think I need to read more, after reading I will understand what you mean. Actually I didn't do testing before expect in Go, which is very straight forward. But didn't get deeper in in testing.