| ||
| ||
Stress Testing, Load Testing and Performance Testing consider as a non-functional testing types. The non-functional testing types are the tests which measure how the system’s works.
The criteria of evaluating inherited from the non-functional requirements. There is an application which can handle 25 simultaneous transactions at a time, with a maximum response per transaction 10 seconds. Example:
In load testing: We will test the application for 25 users and check how application is working in this stage. In performance testing We will concentrate on the time taken to perform the operation. In stress testing: We will test with more users than 25 and the test will continue to any number and we will check where the application is cracking.
Regards, Samer Desouky ISTQB Certified Test Manager Test Leader, MCS
20, Dec 2010 12:48 PM | ||
| 0 Comments | Permanent Link |
| ||
Let’s agreed at the beginning on the test conditions/scenarios is what we need to test and the test cases/procedures is how we’ll test and prove that.
At first, let’s go through a test analysis strategy inherited from the Risk-Based Testing.
First of all, the software requirements are the mentor of the affinity diagrams.
It’s the layers strategy; classify your test item into the following four layers: - Business layer. - Application layer. - Database layer. - Integration layer.
Each layer has its own attributes which in mix with the affinity diagrams will be create the test diagrams for your test items. The business layer briefly, talks about the business processes need to be implemented and tested. The application layer briefly, considers the GUI and data validation scenarios which cover the application movements and data correctness The database layer briefly, covers the data manipulation scenarios and the data itself affection The integration layer briefly, focus in two areas internal and external integration Each layer has the three common paths, primary, alternative and expectations. Now let’s take an example for save as MS-Word. The BL here, save a copy from a document in same folder with different name or same name in different folder. The AL here, using a shortcut key, use the command from menu, use a function key. The DBL here, using special characters, or using special name conditions The IL here, about import file and save it, save into network path, etc... Now can you create a test procedure for the mentioned test scenarios or cases? Regards, Samer Desouky Test Leader, MCS ISTQB CTAL-TM 21, Nov 2010 12:59 PM
| ||
| 0 Comments | Permanent Link |
| ||
Fault Masking is an occurrence, in which one defect prevents the detection of another, It’s a used technique to prevent error result from appearing. For example, if the “Negative Value” cause a system unhandled exception firing, the developer prevents the negative values input instead to handle it, implicitly it solve the issue and prevent another defect from appearing but explicitly if the values entered manually in the database and the system goes to retrieve it, an unhandled exception may fires. So, as a test engineer you can uncover it by using the Grey Box techniques by enter the data manually in the database and try to retrieve it by the application. And it can be uncovered by executing a test case which created based on an Equivalence Partitioning design technique. For more information please contact me. Samer Desouky, Test Leader, MCS ISTQB Certified 28/02/2010 12:37 PM
| ||
| 0 Comments | Permanent Link |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Once upon a time, a huge company was suffered from dealing with the local and the international software houses regarding to the time commitments, cost, and support. They believe that the application quality is the most important benefit to achieve their business targets, they seek for quality. They thought when they deal with a software house ranked in TMM or CMMi, they will get all quality characteristics. They have many questions about, and they have the expected answers too, they believe that the Quality Characteristics will answer them.
They fail to found a software house can realize their needs, The CEO decide to go to utopia to deal with the biggest software house in, but it wasn’t strange that they didn’t found any software house in utopia, Because there is no developers live in there, they always make mistakes. Samer Desouky, Test Leader, MCS ISTQB Certified 18/01/2010 11:34 AM | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 0 Comments | Permanent Link |
| ||
Bugs are important for the testing team like diamonds for the women. Funny statement , let’s see how we can map the 4 C's which are four variables that are used to calculate the value of a diamond to be used to evaluate bugs, “Clarity, Color, Cut, and Carat Weight”.
But first let us define the term bug which will be used here,
The ISTQB standards define a cycle about, A human being can make error/mistake which produces a defect/fault/bug/ in the code, in software or a system, or in a document. If a defect in code is executed, the system will fail to do what it should do (or do something it shouldn’t), and causing a failure.
We’ll use the term Bug instead of failure.
Bug Clarity describes the clearness or purity of a bug. This is determined by the effect, and location of the internal (inclusions) and external (blemishes) imperfections. Based on that we can define the most defected area and describes the Defect Clustering, Bug Color describes the impact and cause. Bug Cut describes the severity. This can range from cosmetics to showstoppers, business or GUI, Low or critical, the categorization of the business processes and the testing analysis layers impacting the severity clustering, we can assume the severity clustering based on the layers (Business, Application, Database and Integration layers). Bug Carat is the unit of weight for the bugs, we can simulate it by the generated values from the Risk Based Testing/Analysis for each test case we can measure it with the found bugs per each test case. Samer Desouky, Test Leader, MCS ISTQB Certified 17/12/2009 11:37 AM | ||
| 0 Comments | Permanent Link |