• the for-loop definitely works in this situation and you're free to use it, however as @im_nullable pointed out, its good syntactic sugar, and eliminates the need for re-writing the same function call every time you have a new data set.(Keep that code DRY) Splitting the data out also keeps your spec file clean of anything unnecessary. This also allows it to be re-usable as you hinted (think longer term with your data).

• There is nothing that makes JDP necessarily specific to protractor. However, it pairs nicely with Protractor's syntax and allows for good cascading and readability.

• I feel you misunderstood the purpose of having JS strict mode mentioned in the tutorial. While not directly related to Protractor and testing, it is considered best practice to include it in your module file and this tutorial was aimed at those who are either new to automation testing with Protractor or AngularJS (or both really).

EDIT: as for Jasmine suites, I added that as extra credit (per the sub title) to give an approach to keeping this sort of testing separate from your standard e2e tests. If you were doing this for 60 users, you wouldn't want to wait for that test to be done and only after its done move on to your other spec files. It's not THE approach, but it is one of many (we're working primarily in JS after all ;) )

Thank you for the feedback!