Added usage example with mistral common
Browse files
    	
        README.md
    CHANGED
    
    | 
         @@ -418,4 +418,34 @@ You can run Devstral using the [Ollama](https://ollama.ai/) CLI. 
     | 
|
| 418 | 
         | 
| 419 | 
         
             
            ```bash
         
     | 
| 420 | 
         
             
            ollama run devstral
         
     | 
| 421 | 
         
            -
            ```
         
     | 
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
|
| 
         | 
| 
         | 
|
| 418 | 
         | 
| 419 | 
         
             
            ```bash
         
     | 
| 420 | 
         
             
            ollama run devstral
         
     | 
| 421 | 
         
            +
            ```
         
     | 
| 422 | 
         
            +
             
     | 
| 423 | 
         
            +
            ### Example: Understanding Test Coverage of Mistral Common
         
     | 
| 424 | 
         
            +
             
     | 
| 425 | 
         
            +
            We can start the OpenHands scaffold and link it to a repo to analyze test coverage and identify badly covered files.
         
     | 
| 426 | 
         
            +
            Here we start with our public `mistral-common` repo.
         
     | 
| 427 | 
         
            +
             
     | 
| 428 | 
         
            +
             
     | 
| 429 | 
         
            +
            After the repo is mounted in the workspace, we give the following instruction
         
     | 
| 430 | 
         
            +
            ```
         
     | 
| 431 | 
         
            +
            Check the test coverage of the repo and then create a visualization of test coverage. Try plotting a few different types of graphs and save them to a png.
         
     | 
| 432 | 
         
            +
            ```
         
     | 
| 433 | 
         
            +
            The agent will first browse the code base to check test configuration and structure.
         
     | 
| 434 | 
         
            +
             
     | 
| 435 | 
         
            +
            
         
     | 
| 436 | 
         
            +
             
     | 
| 437 | 
         
            +
            Then it sets up the testing dependencies and launches the coverage test:
         
     | 
| 438 | 
         
            +
             
     | 
| 439 | 
         
            +
            
         
     | 
| 440 | 
         
            +
             
     | 
| 441 | 
         
            +
            Finally, the agent writes necessary code to visualize the coverage.
         
     | 
| 442 | 
         
            +
            
         
     | 
| 443 | 
         
            +
             
     | 
| 444 | 
         
            +
            At the end of the run, the following plots are produced:
         
     | 
| 445 | 
         
            +
            
         
     | 
| 446 | 
         
            +
            
         
     | 
| 447 | 
         
            +
            
         
     | 
| 448 | 
         
            +
             
     | 
| 449 | 
         
            +
             
     | 
| 450 | 
         
            +
             
     | 
| 451 | 
         
            +
             
     |