[Docs] "Testing your application" page contains beta release information

[dhmlau]

Description / Steps to reproduce / Feature proposal

Originated from the docs cleanup spike: #1908

The "Testing your application" page seems to be outdated.

• "Create a stub service" section
  • a WIP note
  • "The initial beta release does not include Services as a first-class feature." <-- we are no longer in beta release. This should be updated.
• "Perform an auto-generated smoke test of your REST API" section
  • it says "It will be revisited after our MVP release".

@bajtos, I don't have enough knowledge in this area to have a more complete acceptance criteria. It seems like this page needs to be reviewed more thoroughly, rather than just catching the obvious. Thanks.

[bajtos]

"Create a stub service" section

IMO, we should add content to this section, using "Create a stub Repository" for inspiration and 7ceb2c4 for an example code.

"Perform an auto-generated smoke test of your REST API" section
it says "It will be revisited after our MVP release".

Let's modify the warning. Design-first approach is out of scope of 2018Q1, I think we need to use a warning that will work for longer term.

Very loosely related: #644 A better tool for automated API smoke tests

[jannyHou]

Thanks @dhmlau and @bajtos according to the discussion the acceptance criteria would be:

Acceptance criteria:

• Add content to "Create a stub Repository"
  • using "Create a stub Repository" for inspiration and 7ceb2c4 for an example code.
• Add warning to ""Perform an auto-generated smoke test of your REST API" section"
  • Let's modify the warning. Design-first approach is out of scope of 2018Q1, I think we need to use a warning that will work for longer term.

[bajtos]

Add content to "Create a stub Repository"
using "Create a stub Repository" for inspiration and 7ceb2c4 for an example code.

See also #2185