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

Quality Assurance #4

Open
broad-well opened this issue Apr 11, 2018 · 1 comment
Open

Quality Assurance #4

broad-well opened this issue Apr 11, 2018 · 1 comment
Labels
standard Corresponds to the standards used throughout the project, such as documentation & design heuristics.

Comments

@broad-well
Copy link
Member

Developers' own effort in assuring the quality of their code is within the criteria for disciplined software. Certain methodologies should be prescribed as standards in order to minimize bugs and maximize reliability. Ideally, teams should never come to us to report bugs in the core module (how embarrassing!)

@broad-well broad-well added the standard Corresponds to the standards used throughout the project, such as documentation & design heuristics. label Apr 11, 2018
@broad-well
Copy link
Member Author

broad-well commented Apr 11, 2018

As demonstrated, I am a big proponent for Test-Driven or Behavior-Driven Development. There are numerous articles online that discuss their effectiveness and possible shortcomings.

See this article for a thorough definition.

Along with TDD, there should be integration and acceptance tests (or their equivalent) to ensure that the code "works" overall.

LakeYin added a commit that referenced this issue Nov 2, 2018
Merging the fixed ARC Core Code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
standard Corresponds to the standards used throughout the project, such as documentation & design heuristics.
Projects
None yet
Development

No branches or pull requests

1 participant