Add docs on generating stubs

Signed-off-by: Sanjula Ganepola <Sanjula.Ganepola@ibm.com>

Author: SanjulaGanepola

src/content/docs/developing/testing/Testing_GeneratedTestStub.png

@@ -17,6 +17,7 @@ import { Aside, CardGrid, Card } from '@astrojs/starlight/components';
 
 The [IBM i Testing](https://marketplace.visualstudio.com/items?itemName=IBM.vscode-ibmi-testing) extension allows developers to run unit tests and generate code coverage results for RPG and COBOL programs on IBM i. Under the covers, this extension leverages the [RPGUnit](https://irpgunit.sourceforge.io/help) testing framework.
 
+* ✍️ **Generate Stubs**: Generate test stubs for individual test cases or an entire test suite.
 * 👨‍💻 **Run Tests**: Visualize and run tests suites out of local files or source members.
 * ⚙️ **Configure Tests**: Configure parameters to compile (`RUCRTRPG`/`RUCRTCLB`) and run (`RUCALLTST`) tests.
 * 📋 **View Test Results**: View detailed test results along with inline failure/error messages.

src/content/docs/developing/testing/Testing_GeneratingTestStubs.png

@@ -4,7 +4,7 @@ title: Writing Tests
 
 import { Aside, CardGrid, Card, Tabs, TabItem } from '@astrojs/starlight/components';
 
-## Naming Conventions
+## Naming Requirements
 
 ### Test Cases
 
@@ -111,7 +111,15 @@ In order to use RPGUnit procedures you need to add the `TESTCASE` copybook to yo
   </TabItem>
 </Tabs>
 
-## Generating Stubs
+## Generating Test Stubs
+
+To simplify the process of writing tests, you can have the extension generate stubs for individual test cases or an entire test suite. To do this, place your cursor inside any export procedure and click the code action button (💡). This will give you an option to generate a test case for the specific procedure you are in or to generate a test suite containing test cases for every procedure.
+
+![Generating Test Stubs](Testing_GeneratingTestStubs.png)
+
+After selecting an option, a test suite will be created if it does not already exist with a scaffold that will include not only the test case stubs, but also the necessary includes and prototypes (if necessary). The generated test case stubs themselves will each be structured into the following sections: declarations, inputs, actual results, expected results, and assertions. As the developer, you will need to fill in the inputs and expected results.
+
+![Generated Test Stub](Testing_GeneratedTestStub.png)
 
 ## Example Test Suites
 
@@ -120,5 +128,5 @@ To get started with some sample tests, check out these examples:
 * RPGUnit [templates](https://github.com/tools-400/irpgunit/tree/main/host/iRPGUnit/QTEMPLATE) and [self tests](https://github.com/tools-400/irpgunit/tree/main/host/iRPGUnit/QTESTCASES)
 
 <Aside type="tip">
-  If you have example tests that you would like to share with the community, please open a pull request [here](https://github.com/codefori/docs) to add them to this page.
+  🙏 If you have example tests that you would like to share with the community, please open a pull request [here](https://github.com/codefori/docs) to add them to this list!
 </Aside>