Software testing
Description:
Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. In simple words, testing is executing a system in order to identify any gaps, errors, or missing requirements in contrary to the actual requirements.
Links:
https://www.tutorialspoint.com/software_testing/software_testing_quick_guide.htm
https://testlio.com/blog/get-started-software-testing/
Keywords:
testing, qa, software, test cases, development
Motivation:
The automated testing that was presented, when each developer does his own tests, is classically used here. We also use so-called monkey testing, which some testers enjoy and will continue to use. For monkey testing, we also use semi-automated tests created in Selenium IDE, which makes our work very easy at the moment. I understand that monkey testing is not very representative, but I trust it more than automated tests.
Requirements/Prerequisities:
Test Strategy, Testing Plan, Test Cases, Test Data, Test Environment.
Level:
concret: specific best practice (e.g. use microservice)
Application domain:
Software engineering
Main phase:
Development: Testing
Related literature:
https://www.tutorialspoint.com/software_testing/software_testing_quick_guide.htm
https://testlio.com/blog/get-started-software-testing/
In which projects do/did you use this practice?
PROFI.neo (DGR), InfoWIN-Touch (Windhager), HuSEIA (ENGEL), SmartMatch (TIGER)
Software Tester
6–10 years of experiences
Masaryk University
| 1. How do you rate the potential benefit for your projects? | 4 |
| 2. How often are you using that practice? | 5 |
| 3. What is the effort to introduce the practice in your project upfront? | 3 |
| 4. What is the effort to apply the best practice in your project daily basis? | 4 |
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)