Repository: dbt-labs/dbt-core
Pull request: Update implementation-ticket.yml
resolves #9348 

### Problem

We spend time in estimation meetings talking about what specific tickets should be testing,

### Solution

Add a specific section for testing to our template.

### Checklist

- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md) and understand what's expected of me  
- [ ] I have run this code in development and it appears to resolve the stated issue  
- [ ] This PR includes tests, or tests are not required/relevant for this PR
- [ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
- [ ] This PR includes [type annotations](https://docs.python.org/3/library/typing.html) for new and modified functions


Problem statement:
[CT-3531] Add testing section to Implementation template
### Housekeeping

- [X] I am a maintainer of dbt-core

### Short description

Add a "Suggested Tests" section to the implementation issue template.  

### Acceptance criteria

"Suggested Tests" section to the implementation issue template.

### Impact to Other Teams

None

### Will backports be required?

No

### Context

This will standardize adding tests to issues we create.

Hints from issue discussion:

Commit message: Update implementation-ticket.yml

Patch to review:
diff --git a/.github/ISSUE_TEMPLATE/implementation-ticket.yml b/.github/ISSUE_TEMPLATE/implementation-ticket.yml
index e5bfaaa45e5..4187816d1fe 100644
--- a/.github/ISSUE_TEMPLATE/implementation-ticket.yml
+++ b/.github/ISSUE_TEMPLATE/implementation-ticket.yml
@@ -30,6 +30,17 @@ body:
         What is the definition of done for this ticket? Include any relevant edge cases and/or test cases
     validations:
       required: true
+  - type: textarea
+    attributes:
+      label: Suggested Tests
+      description: |
+        Provide scenarios to test.  Link to existing similar tests if appropriate.
+    placeholder: |
+        Example: |
+          1. Test with no version specified in the schema file and use selection logic on a versioned model for a specific version.  Expect pass.
+          2. Test with a version specified in the schema file that is no valid.  Expect ParsingError.
+    validations:
+      required: false
   - type: textarea
     attributes:
       label: Impact to Other Teams
@@ -53,6 +64,5 @@ body:
       label: Context
       description: |
         Provide the "why", motivation, and alternative approaches considered -- linking to previous refinement issues, spikes, Notion docs as appropriate
-          validations:
     validations:
       required: false


Code review comments:
diff_hunk: @@ -30,6 +30,17 @@ body:
         What is the definition of done for this ticket? Include any relevant edge cases and/or test cases
     validations:
       required: true
+  - type: textarea
+    attributes:
+      label: Suggested Tests
+      description: |
+        Provide scenarios to test.  Link to existing similar tests if appropriate.
+    placeholder: |
+        Example: |
+          1. Test with no version specified in the schema file and use selection logic on a versioned model for a specific version.  Expect pass.
+          2. Test with a version specified in the schema file that is no valid.  Expect ParsingError.
+    validations:
+      required: false
path: .github/ISSUE_TEMPLATE/implementation-ticket.yml
text: @author:
```suggestion
      required: true
```