Abstract
Quality refers to the degree to which software does what it’s supposed to do, and is built in a way that is structurally sound. Testing refers to checking and giving feedback on software quality. Testing can assess functional quality: does it do what it’s supposed to do and not do things it shouldn’t? Testing can also assess structural quality: is it reliable, secure, maintainable, performant, and appropriately sized?
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
- 2.
- 3.
Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship (Prentice Hall, 2008).
- 4.
Deming, W E. Out of the Crisis. Cambridge, Mass: Massachusetts Institute of Technology, Center for Advanced Engineering Study, 1986. Print.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
Nicole Forsgren, Jez Humble, and Gene Kim, Accelerate: The Science of Lean Software and Devops Building and Scaling High Performing Technology Organizations (IT Revolution Press, 2018): p. 79
- 34.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Andrew Davis
About this chapter
Cite this chapter
Davis, A. (2019). Quality and Testing. In: Mastering Salesforce DevOps . Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5473-8_8
Download citation
DOI: https://doi.org/10.1007/978-1-4842-5473-8_8
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-5472-1
Online ISBN: 978-1-4842-5473-8
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books