TEST THE RISK!

Test it or let the customers do it in wild! Testing is not a state it is a process, any failures in the process, make the quality ruined. Moreover, any failures detected in any part of a product make the product fail in terms of customers. Therefore we need to deploy the quality as a process of products and services which are given to customers along the product life cycle. In this post, I want to explain the importance of testing with the case of the successful Korean technology company 'Samsung'. The real problem with the product is that design of the battery has some defective points because they want to push boundaries too much for having more power small battery cell. For more detail, you can this post . Let's look at product life cycle management (PLM) first. It explains a product from an idea to delivering a product and terminating support. It divides the product life cycle management into four main stages as follows: Conceive  : Imagine, specify, plan, innovate Des

Test strategy or test approach; the meanings of these two terms are generally confused. However, the test strategy is more general and says more than test approach. The testing approach can be explained by groups of test type which are aimed to use for a more successful result by including all the component of the project. By defining the testing approach, test teams can be more comfortable for finding defects. To define the testing approach the following items should be evaluated: Software development methodologies Customer requirements Testing objectives Project subjects Test team knowledge Etc. For sample test approach ISTQB suggests the following approaches: If the test approach is clarified then the definition of the test strategy can be easier. Test strategy is the rules which draw the border of the test approach. It lets people in the project know how to react and it is used for designing of the test cases, defining the process, entry criteria and exit criteria. Ac