Skip to content
This repository has been archived by the owner on Jan 26, 2021. It is now read-only.

Document Automated Testing in VMS #779

Closed
4 of 7 tasks
Monal5031 opened this issue Jul 3, 2018 · 4 comments
Closed
4 of 7 tasks

Document Automated Testing in VMS #779

Monal5031 opened this issue Jul 3, 2018 · 4 comments
Assignees
Labels
Category: Documentation/Training Improvements or additions to documentation. Category: Quality Assurance Changes to code or files that improve testing or fixes bugs. Program: GSOC Related to work completed during the Google Summer of Code Program.

Comments

@Monal5031
Copy link
Contributor

Monal5031 commented Jul 3, 2018

Description

As a developer, I should document all the work I have done so that it can be used by future developers as reference and making it easy to contribute to the project.

Mocks

N/A

Acceptance Criteria

Update [Required]

  • Document failing test with failure reason and corresponding issue
  • Document Installation setup
  • Document Design Document
  • Document existing tests with docstrings.
  • Document a short tutorial for automated testing in repo.

Definition of Done

  • All of the required items are completed.
  • Approval by 2 mentor.

Estimation

14-16 hours

@Monal5031 Monal5031 added Type: Enhancement New feature or request. Category: Documentation/Training Improvements or additions to documentation. Category: Quality Assurance Changes to code or files that improve testing or fixes bugs. Program: GSOC Related to work completed during the Google Summer of Code Program. labels Jul 3, 2018
@Monal5031 Monal5031 self-assigned this Jul 3, 2018
@ayushgarg1804
Copy link

Adding docstrings in the tests will really help too.

@ayushgarg1804 ayushgarg1804 added Type: Maintenence and removed Type: Enhancement New feature or request. labels Jul 3, 2018
@Monal5031
Copy link
Contributor Author

@ayushgarg1804 I was thinking to create a separate doc to explain test cases 1-2 line each wouldnt docstrings repeat the same thing then?
Since tests dont have return vals and params so docstrings will only have test case description only.

@Monal5031
Copy link
Contributor Author

Or shall I only document them in docstrings only and not a separate document?

@ayushgarg1804
Copy link

Its up to you actually. If you document them in docstrings you can automatically create a documentation from it and if you create a separate document then it will me more personalized and specific.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Category: Documentation/Training Improvements or additions to documentation. Category: Quality Assurance Changes to code or files that improve testing or fixes bugs. Program: GSOC Related to work completed during the Google Summer of Code Program.
Projects
None yet
Development

No branches or pull requests

2 participants