A subcommand to initialize a new test script file

[andrewslotin]

Feature Description

A new k6 script requires writing some boilerplate code. For new users this requires reading the documentation before being able to execute their first k6 run, which creates an additional entry barrier, while for experienced users it's a tedious task that could have been automated.

Suggested Solution (optional)

I propose to add a new init subcommand to k6 that creates a JS file containing a minimal k6 script that can be executed with k6 run. As a content of this file I'd propose the simple local script from the docs:

import http from 'k6/http';
import { sleep } from 'k6';

export default function () {
  http.get('https://test.k6.io');
  sleep(1);
}

I'd also consider adding the code that enables running browser tests, i.e. the options.scenarios section that enables Browser API, and have it commented out similar to what vagrant init does.

Already existing or connected issues / PRs (optional)

No response