torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improved prompt for next steps

Browse Source
This commit is contained in:
Fahad
2025-06-14 15:51:04 +04:00
parent 4086306c58
commit acbfa1c94e
2 changed files with 9 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tests/test_testgen.py
View File

@@ -285,8 +285,8 @@ class TestComprehensive(unittest.TestCase):
# Check formatting includes next steps # Check formatting includes next steps
assert raw_response in formatted assert raw_response in formatted
assert "**Next Steps:**" in formatted assert "**Next Steps:**" in formatted
assert "Review Generated Tests" in formatted assert "Create and save the test files" in formatted
assert "Setup Test Environment" in formatted assert "Run the tests" in formatted
@pytest.mark.asyncio @pytest.mark.asyncio
async def test_error_handling_invalid_files(self, tool): async def test_error_handling_invalid_files(self, tool):

16
tools/testgen.py
View File

@@ -412,18 +412,16 @@ class TestGenTool(BaseTool):
**Next Steps:** **Next Steps:**
1. **Review Generated Tests**: Check if the structure, coverage, and edge cases are valid and useful. Ensure they meet your requirements. Claude must now:
Confirm the tests cover missing scenarios, follow project conventions, and can be safely added without duplication.
2. **Setup Test Environment**: Ensure the testing framework and dependencies identified are properly configured in your project. 1. **Create and save the test files** - Write the generated tests to appropriate test files in your project structure
3. **Run Initial Tests**: Execute the generated tests to verify they work correctly with your code. 2. **Display to the user** - Show each new test file/function created with a brief line explaining what it covers
4. **Customize as Needed**: Modify generated test code, add project-specific edge cases, refine or adjust test structure based on your specific needs if deemed necessary 3. **Install any missing test dependencies** - Set up required testing frameworks if not already available
based on your existing knowledge of the code.
5. **Integrate with CI/CD**: Add the tests to your continuous integration pipeline to maintain code quality if this has already been setup and available. 4. **Run the tests** - Execute the test suite to verify functionality and fix any issues
6. Refine requirements and continue the conversation if additional coverage or improvements are needed. 5. **Integrate the tests** - Ensure tests are properly connected to your existing test infrastructure
Remember: Review the generated tests for completeness and adapt and integrate them to your specific project requirements and testing standards. Continue with your next step in implementation.""" The tests are ready for immediate implementation and integration into your codebase."""