Software testing | Wikipedia audio article
Channel: wikipedia tts
Date: 11/01/2019

This is an audio version of the Wikipedia Article:
https://en.wikipedia.org/wiki/Software_testing


00:02:36 1 Overview
00:04:58 1.1 Defects and failures
00:06:28 1.2 Input combinations and preconditions
00:07:51 1.3 Economics
00:08:26 1.4 Roles
00:09:11 2 History
00:09:49 3 Testing approach
00:09:58 3.1 Static vs. dynamic testing
00:11:10 3.2 Exploratory approach
00:11:59 3.3 The "box" approach
00:12:47 3.3.1 White-box testing
00:15:59 3.3.2 Black-box testing
00:19:56 3.3.2.1 Visual testing
00:22:04 3.3.3 Grey-box testing
00:24:01 4 Testing levels
00:24:48 4.1 Unit testing
00:26:41 4.2 Integration testing
00:27:37 4.3 System testing
00:28:10 4.4 Operational acceptance testing
00:29:17 5 Testing types, techniques and tactics
00:29:38 5.1 Installation testing
00:30:04 5.2 Compatibility testing
00:31:19 5.3 Smoke and sanity testing
00:31:51 5.4 Regression testing
00:33:28 5.5 Acceptance testing
00:34:09 5.6 Alpha testing
00:34:39 5.7 Beta testing
00:35:29 5.8 Functional vs non-functional testing
00:36:42 5.9 Continuous testing
00:37:24 5.10 Destructive testing
00:38:13 5.11 Software performance testing
00:40:05 5.12 Usability testing
00:40:25 5.13 Accessibility testing
00:40:59 5.14 Security testing
00:41:41 5.15 Internationalization and localization
00:44:32 5.16 Development testing
00:45:41 5.17 A/B testing
00:46:14 5.18 Concurrent testing
00:46:42 5.19 Conformance testing or type testing
00:47:10 5.20 Output comparison testing
00:47:43 6 Testing process
00:47:52 6.1 Traditional waterfall development model
00:48:48 6.2 Agile or XP development model
00:50:21 6.3 A sample testing cycle
00:52:59 7 Automated testing
00:53:48 7.1 Testing tools
00:55:20 8 Measurement in software testing
00:56:01 8.1 Hierarchy of testing difficulty
00:58:45 9 Testing artifacts
01:03:36 10 Certifications
01:05:39 11 Controversy
01:10:09 12 Related processes
01:10:19 12.1 Software verification and validation
01:14:54 12.2 Software quality assurance (SQA)
01:16:19 13 See also



Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

Listen on Google Assistant through Extra Audio:
https://assistant.google.com/services/invoke/uid/0000001a130b3f91
Other Wikipedia audio articles at:
https://www.youtube.com/results?search_query=wikipedia+tts
Upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts
Speaking Rate: 0.8452269107893294
Voice name: en-US-Wavenet-E


"I cannot teach anybody anything, I can only make them think."
- Socrates


SUMMARY
=======
Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include the process of executing a program or application with the intent of finding software bugs (errors or other defects), and verifying that the software product is fit for use.
Software testing involves the execution of a software component or system component to evaluate one or more properties of interest. In general, these properties indicate the extent to which the component or system under test.

meets the requirements that guided its design and development,
responds correctly to all kinds of inputs,
performs its functions within an acceptable time,
it is sufficiently usable,
can be installed and run in its intended environments, and
achieves the general result its stakeholders desire.As the number of possible tests for even simple software components is practically infinite, all software testing uses some strategy to select tests that are feasible for the available time and resources. As a result, software testing typically (but not exclusively) attempts to execute a program or application with the intent of finding software bugs (errors or other defects). The job of testing is an iterative process as when one bug is fixed, it can illuminate other, deeper bugs, or can even create new ones.
Software testing can provide objective, independent information about the quality of software and risk of its failure to users or sponsors.Software testing can be conducted as soon as executable software (even if partially complete) exists. The overall approach to software development often deter ...