Posted by Andrew Matsa Aug 19th, 2013
Hello to all test engineers and all people who are reading Drucode blog. Today I will tell you about testing in general and test processes on projects run by me at Drucode.
There is such a dictum in testing called "Monkey testing". It states, that if we put a monkey in front of the computer, it will click anywhere randomly and will eventually find bugs. Some companies might be successful employing such an approach. At Drucode it’s not a case.
Though if there’s a monkey that can really build test processes, we will gladly invite it for the interview.
Actually, developers and testers are completely different people in the life cycle of software product. They contribute/develop in different ways. The only thing that should unite us - is the strive for a high-quality end-product.
Testing - is the process of verifying whether a developed product is in alignment with a given specification. This process is a rather extensive concept because it includes a variety of techniques and methodologies to be followed. Failure to do so may cause its irrational recurrence.
We different testing strategies for different projects.
Imagine we have an objective (and, in fact, it’s a true objective for 99% of our projects) to implement a “Pixel Perfect front-end”, that is in alignment with graphic design. In this case, no matter which automation tests are written - we will still need to test front-end work manually, to ensure that the expected result is reached. A GUI testing exists for this purpose. Although there are tools to compare graphic elements, but all of them are still far from being perfectly precise - that's why it is too soon to talk about them as a relevant replacement of manual testing. In another case we'll write auto tests for regression testing or Acceptance testing to save our time and customer's money. For example if product works with big data.
Before the actual testing of web application, it is absolutely needed to know the scope of work to be done on product development. It’s impossible to test the product, without a good knowledge of client’s requirements and proper understanding of the architecture of the future product. However, such types of testing as exploratory testing and error guessing suggest performing testing without prior knowledge of the system that is being tested. Those methods are used for a quick testing, when you are short on time. Those methods effectiveness relays on the experience of the tester (e.g. a good tester knows where defects are more likely to lurk).
All types of testing, test process descriptions I will describe step by step in this blog.
Follow our new blog post on testing.
There is such a dictum in testing called "Monkey testing". It states, that if we put a monkey in front of the computer, it will click anywhere randomly and will eventually find bugs. Some companies might be successful employing such an approach. At Drucode it’s not a case.
Though if there’s a monkey that can really build test processes, we will gladly invite it for the interview.
Actually, developers and testers are completely different people in the life cycle of software product. They contribute/develop in different ways. The only thing that should unite us - is the strive for a high-quality end-product.
Software Testing Process
We different testing strategies for different projects.
Imagine we have an objective (and, in fact, it’s a true objective for 99% of our projects) to implement a “Pixel Perfect front-end”, that is in alignment with graphic design. In this case, no matter which automation tests are written - we will still need to test front-end work manually, to ensure that the expected result is reached. A GUI testing exists for this purpose. Although there are tools to compare graphic elements, but all of them are still far from being perfectly precise - that's why it is too soon to talk about them as a relevant replacement of manual testing. In another case we'll write auto tests for regression testing or Acceptance testing to save our time and customer's money. For example if product works with big data.
Before the actual testing of web application, it is absolutely needed to know the scope of work to be done on product development. It’s impossible to test the product, without a good knowledge of client’s requirements and proper understanding of the architecture of the future product. However, such types of testing as exploratory testing and error guessing suggest performing testing without prior knowledge of the system that is being tested. Those methods are used for a quick testing, when you are short on time. Those methods effectiveness relays on the experience of the tester (e.g. a good tester knows where defects are more likely to lurk).
Types of Testing We Cover
- Functional (Black-Box)
- Installation / Integration / System
- Usability & Graphic User Interfaces (GUI)
- Regression
- Compatibility
- Performance testing / Load / Stress
- Security
- Smoke testing
- Internationalization
- User Acceptance
All types of testing, test process descriptions I will describe step by step in this blog.
Follow our new blog post on testing.