Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track how many characters were present in code part / complete response #128

Closed
8 tasks done
bauersimon opened this issue May 17, 2024 · 2 comments
Closed
8 tasks done
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@bauersimon
Copy link
Member

bauersimon commented May 17, 2024

Tasks

  • Introduce 2 assessment keys:
    • AssessmentKeyResponseCharacterCount
    • AssessmentKeyGenerateTestsForFileCharacterCount
  • LLM model
    • File: model/llm/llm.go
    • Function: GenerateTestsForFile
    • When parsing the model response, count the number of characters of the response and the test content
    • Add it to the assessments
  • Symflower
    • File: model/symflower/symflower.go
    • Function: GenerateTestsForFile
    • Get the output of the symflower unit-tests command
    • Parse the output and return the list of test files generated
    • For each generated file, read its content and count the characters
      • Note: AssessmentKeyResponseCharacterCount == AssessmentKeyGenerateTestsForFileCharacterCount
@bauersimon bauersimon added the enhancement New feature or request label May 17, 2024
@bauersimon bauersimon added this to the v0.5.0 milestone May 17, 2024
@bauersimon bauersimon self-assigned this May 17, 2024
@zimmski zimmski assigned ruiAzevedo19 and unassigned bauersimon May 24, 2024
@zimmski
Copy link
Member

zimmski commented May 24, 2024

AssessmentKeyCharacterCountResponse
AssessmentKeyCharacterCountGeneratedTests

Just looked into what we have right now. Let's do the following to better group assessments:

AssessmentKeyResponseCharacterCount
AssessmentKeyGenerateTestsForFileCharacterCount

@zimmski
Copy link
Member

zimmski commented May 24, 2024

Test it

I think you can always drop that task. Should go without saying. Every task you do should be tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants