[ 
https://issues.apache.org/jira/browse/DRILL-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Farkas updated DRILL-6249:
----------------------------------
    Description: I am working on a presentation about how to use the unit 
testing utilities in Drill. Instead of writing the doc and having it be lost in 
Google Drive somewhere I am going to add a Markdown doc to the drill repo and 
link to it in the README.md. This is appropriate since these docs will only be 
used by developers, and the way we unit test will change as the code changes. 
So the unit testing docs should be kept in the same repo as the code so it can 
be updated and kept in sync with the rest of Drill.  (was: I am working on a 
presentation about how to use the unit testing utilities in Drill. Instead of 
writing the doc and having it be lost in Google Drive somewhere I am going to 
add a Markdown doc to the drill repo and link to it in the README.md. This is 
appropriate since these docs will only be used by developers, and the way we 
unit test will change as the code changes. So the unit testing docs should be 
kept in the same repo as the code.)

> Add Markdown Docs for Unit Testing and Link to it in README.md
> --------------------------------------------------------------
>
>                 Key: DRILL-6249
>                 URL: https://issues.apache.org/jira/browse/DRILL-6249
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: Timothy Farkas
>            Assignee: Timothy Farkas
>            Priority: Major
>
> I am working on a presentation about how to use the unit testing utilities in 
> Drill. Instead of writing the doc and having it be lost in Google Drive 
> somewhere I am going to add a Markdown doc to the drill repo and link to it 
> in the README.md. This is appropriate since these docs will only be used by 
> developers, and the way we unit test will change as the code changes. So the 
> unit testing docs should be kept in the same repo as the code so it can be 
> updated and kept in sync with the rest of Drill.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to