Currently it is possible to write a custom slash command in Continue in order to generate unit tests, but this is a prominent enough use case that we'll probably want dedicated UI and prompts.
If you were interested in this, the best place to start might be trying out different prompts to generate unit tests. Some great work was done by Meta in this paper: https://arxiv.org/abs/2402.09171
Another area of work will be determining the best user workflow to generate these tests. Should they be generated in the background? Every time a new function is added? Only when triggered by a user? In CI? Probably a promising and simple place to start would be a new page in the gui/src/pages folder, which would show up in the sidebar and give some dedicated UI.
Currently it is possible to write a custom slash command in Continue in order to generate unit tests, but this is a prominent enough use case that we'll probably want dedicated UI and prompts.
If you were interested in this, the best place to start might be trying out different prompts to generate unit tests. Some great work was done by Meta in this paper: https://arxiv.org/abs/2402.09171
Another area of work will be determining the best user workflow to generate these tests. Should they be generated in the background? Every time a new function is added? Only when triggered by a user? In CI? Probably a promising and simple place to start would be a new page in the
gui/src/pagesfolder, which would show up in the sidebar and give some dedicated UI.