ºÝºÝߣshows by User: AndreVerschelling / http://www.slideshare.net/images/logo.gif ºÝºÝߣshows by User: AndreVerschelling / Wed, 23 Nov 2016 13:29:02 GMT ºÝºÝߣShare feed for ºÝºÝߣshows by User: AndreVerschelling NLTestDag_20161118-B /slideshow/nltestdag20161118b/69455765 1276ebf2-2c7f-48aa-9b6b-dcb4f04d6c37-161123132903
]]>
]]> Wed, 23 Nov 2016 13:29:02 GMT /slideshow/nltestdag20161118b/69455765 AndreVerschelling@slideshare.net(AndreVerschelling) NLTestDag_20161118-B AndreVerschelling <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/1276ebf2-2c7f-48aa-9b6b-dcb4f04d6c37-161123132903-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
NLTestDag_20161118-B from Andre Verschelling
]]> 552 6 https://cdn.slidesharecdn.com/ss_thumbnails/1276ebf2-2c7f-48aa-9b6b-dcb4f04d6c37-161123132903-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 The good the bad and the ugly - final /slideshow/the-good-the-bad-and-the-ugly-final/56641088 d5116a55-73e2-4061-915a-97150ddd4667-160104084746
]]>
]]> Mon, 04 Jan 2016 08:47:46 GMT /slideshow/the-good-the-bad-and-the-ugly-final/56641088 AndreVerschelling@slideshare.net(AndreVerschelling) The good the bad and the ugly - final AndreVerschelling <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/d5116a55-73e2-4061-915a-97150ddd4667-160104084746-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
The good the bad and the ugly - final from Andre Verschelling
]]> 396 6 https://cdn.slidesharecdn.com/ss_thumbnails/d5116a55-73e2-4061-915a-97150ddd4667-160104084746-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 No Test without Integration - final /slideshow/no-test-without-integration-final/56641037 27211af3-0cda-4fc9-a24d-9d01c127e52d-160104084529
]]>
]]> Mon, 04 Jan 2016 08:45:29 GMT /slideshow/no-test-without-integration-final/56641037 AndreVerschelling@slideshare.net(AndreVerschelling) No Test without Integration - final AndreVerschelling <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/27211af3-0cda-4fc9-a24d-9d01c127e52d-160104084529-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
No Test without Integration - final from Andre Verschelling
]]> 458 8 https://cdn.slidesharecdn.com/ss_thumbnails/27211af3-0cda-4fc9-a24d-9d01c127e52d-160104084529-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Testautomatisering? Ik zeg, doen! /slideshow/testautomatisering-29-nov-2011-nl-20111125/35375595 testautomatisering29nov2011-nl20111125-140602030722-phpapp02
Keynote (Dutch) held at a customer event of Sogeti High Tech Netherlands on test automation. Despite problems of technical nature (how to execute tests on an embedded system for example) or difficult proof of ROI, it is always beneficial to automate tests. Mainly because it helps you to fulfil your chosen test strategy. This keynote was presented at November 29th, 2011, Eindhoven]]>
Keynote (Dutch) held at a customer event of Sogeti High Tech Netherlands on test automation. Despite problems of technical nature (how to execute tests on an embedded system for example) or difficult proof of ROI, it is always beneficial to automate tests. Mainly because it helps you to fulfil your chosen test strategy. This keynote was presented at November 29th, 2011, Eindhoven]]> Mon, 02 Jun 2014 03:07:22 GMT /slideshow/testautomatisering-29-nov-2011-nl-20111125/35375595 AndreVerschelling@slideshare.net(AndreVerschelling) Testautomatisering? Ik zeg, doen! AndreVerschelling Keynote (Dutch) held at a customer event of Sogeti High Tech Netherlands on test automation. Despite problems of technical nature (how to execute tests on an embedded system for example) or difficult proof of ROI, it is always beneficial to automate tests. Mainly because it helps you to fulfil your chosen test strategy. This keynote was presented at November 29th, 2011, Eindhoven <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testautomatisering29nov2011-nl20111125-140602030722-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Keynote (Dutch) held at a customer event of Sogeti High Tech Netherlands on test automation. Despite problems of technical nature (how to execute tests on an embedded system for example) or difficult proof of ROI, it is always beneficial to automate tests. Mainly because it helps you to fulfil your chosen test strategy. This keynote was presented at November 29th, 2011, Eindhoven
Testautomatisering? Ik zeg, doen! from Andre Verschelling
]]> 451 4 https://cdn.slidesharecdn.com/ss_thumbnails/testautomatisering29nov2011-nl20111125-140602030722-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Real life test; real life situations /slideshow/real-life-test-real-life-situations/35375354 reallifetestreallifesituations-20140409-140602025635-phpapp02
Why do customers every now and then find issues we didn’t find, despite all the efforts we put in testing? Is it maybe because we don’t test the system as the customer uses it? Using real-life tests based upon operational profiles will help you find the bugs before your customer does. And in case your customer still finds these nasty intermittent, hard-to-reproduce, problems, the very same technique helps you to pin-point its root cause. This presentation was held at the Dutch Testing Conference 2014, Ede]]>
Why do customers every now and then find issues we didn’t find, despite all the efforts we put in testing? Is it maybe because we don’t test the system as the customer uses it? Using real-life tests based upon operational profiles will help you find the bugs before your customer does. And in case your customer still finds these nasty intermittent, hard-to-reproduce, problems, the very same technique helps you to pin-point its root cause. This presentation was held at the Dutch Testing Conference 2014, Ede]]> Mon, 02 Jun 2014 02:56:35 GMT /slideshow/real-life-test-real-life-situations/35375354 AndreVerschelling@slideshare.net(AndreVerschelling) Real life test; real life situations AndreVerschelling Why do customers every now and then find issues we didn’t find, despite all the efforts we put in testing? Is it maybe because we don’t test the system as the customer uses it? Using real-life tests based upon operational profiles will help you find the bugs before your customer does. And in case your customer still finds these nasty intermittent, hard-to-reproduce, problems, the very same technique helps you to pin-point its root cause. This presentation was held at the Dutch Testing Conference 2014, Ede <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/reallifetestreallifesituations-20140409-140602025635-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Why do customers every now and then find issues we didn’t find, despite all the efforts we put in testing? Is it maybe because we don’t test the system as the customer uses it? Using real-life tests based upon operational profiles will help you find the bugs before your customer does. And in case your customer still finds these nasty intermittent, hard-to-reproduce, problems, the very same technique helps you to pin-point its root cause. This presentation was held at the Dutch Testing Conference 2014, Ede
Real life test; real life situations from Andre Verschelling
]]> 1654 6 https://cdn.slidesharecdn.com/ss_thumbnails/reallifetestreallifesituations-20140409-140602025635-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Do you test the way your customer acts? /slideshow/expo-qa14-andr-verschelling-final/35375222 expoqa14-andrverschelling-final-140602025054-phpapp02
Most of our test efforts pay only attention to verification, 'did we build the system right', and there is a tendency to perform this as much as possible by automated unit tests at code development level followed by exploratory testing at system level. In other cases more formal test design techniques are used, but in both cases, the focus is on the functional behavior of the system or application. But what about validation, 'did we build the right system'? An issue regularly confronted with are problems reported by customers after the system or application has been released, which raises questions like 'why didn't we find that?' and 'how do we reproduce this problem?'. It seems that the customer is using the system in another way as expected, and most of the time the customer is even blamed for that as he or she did not use the system 'asit should be used', at least not the way 'we' think it should be used. To pay more attention to the validation aspects or to perform a problem analysis nevertheless test design techniques can be used. The Statistical UsageTest (SUT) using Operational Profiles is very helpful as it applies a customers' view to your application or product. This presentation shows how to create and apply the SUT in general and a practical example of using it inRoot Cause Analysis is also given. This lecture was presented at expo:QA'14, Madrid]]>
Most of our test efforts pay only attention to verification, 'did we build the system right', and there is a tendency to perform this as much as possible by automated unit tests at code development level followed by exploratory testing at system level. In other cases more formal test design techniques are used, but in both cases, the focus is on the functional behavior of the system or application. But what about validation, 'did we build the right system'? An issue regularly confronted with are problems reported by customers after the system or application has been released, which raises questions like 'why didn't we find that?' and 'how do we reproduce this problem?'. It seems that the customer is using the system in another way as expected, and most of the time the customer is even blamed for that as he or she did not use the system 'asit should be used', at least not the way 'we' think it should be used. To pay more attention to the validation aspects or to perform a problem analysis nevertheless test design techniques can be used. The Statistical UsageTest (SUT) using Operational Profiles is very helpful as it applies a customers' view to your application or product. This presentation shows how to create and apply the SUT in general and a practical example of using it inRoot Cause Analysis is also given. This lecture was presented at expo:QA'14, Madrid]]> Mon, 02 Jun 2014 02:50:54 GMT /slideshow/expo-qa14-andr-verschelling-final/35375222 AndreVerschelling@slideshare.net(AndreVerschelling) Do you test the way your customer acts? AndreVerschelling Most of our test efforts pay only attention to verification, 'did we build the system right', and there is a tendency to perform this as much as possible by automated unit tests at code development level followed by exploratory testing at system level. In other cases more formal test design techniques are used, but in both cases, the focus is on the functional behavior of the system or application. But what about validation, 'did we build the right system'? An issue regularly confronted with are problems reported by customers after the system or application has been released, which raises questions like 'why didn't we find that?' and 'how do we reproduce this problem?'. It seems that the customer is using the system in another way as expected, and most of the time the customer is even blamed for that as he or she did not use the system 'asit should be used', at least not the way 'we' think it should be used. To pay more attention to the validation aspects or to perform a problem analysis nevertheless test design techniques can be used. The Statistical UsageTest (SUT) using Operational Profiles is very helpful as it applies a customers' view to your application or product. This presentation shows how to create and apply the SUT in general and a practical example of using it inRoot Cause Analysis is also given. This lecture was presented at expo:QA'14, Madrid <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/expoqa14-andrverschelling-final-140602025054-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Most of our test efforts pay only attention to verification, &#39;did we build the system right&#39;, and there is a tendency to perform this as much as possible by automated unit tests at code development level followed by exploratory testing at system level. In other cases more formal test design techniques are used, but in both cases, the focus is on the functional behavior of the system or application. But what about validation, &#39;did we build the right system&#39;? An issue regularly confronted with are problems reported by customers after the system or application has been released, which raises questions like &#39;why didn&#39;t we find that?&#39; and &#39;how do we reproduce this problem?&#39;. It seems that the customer is using the system in another way as expected, and most of the time the customer is even blamed for that as he or she did not use the system &#39;asit should be used&#39;, at least not the way &#39;we&#39; think it should be used. To pay more attention to the validation aspects or to perform a problem analysis nevertheless test design techniques can be used. The Statistical UsageTest (SUT) using Operational Profiles is very helpful as it applies a customers&#39; view to your application or product. This presentation shows how to create and apply the SUT in general and a practical example of using it inRoot Cause Analysis is also given. This lecture was presented at expo:QA&#39;14, Madrid
Do you test the way your customer acts? from Andre Verschelling
]]> 369 3 https://cdn.slidesharecdn.com/ss_thumbnails/expoqa14-andrverschelling-final-140602025054-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-AndreVerschelling-48x48.jpg?cb=1528788655 Test consultant and test specialist with a strong focus on quality improvement and a proven track-record in Test Process improvement, Test Management, Test Automation, Test Design Techniques and Test Metrics for embedded systems. Experienced in requirements management, development, integration & test of embedded systems and software. http://www.sogeti.nl https://cdn.slidesharecdn.com/ss_thumbnails/1276ebf2-2c7f-48aa-9b6b-dcb4f04d6c37-161123132903-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/nltestdag20161118b/69455765 NLTestDag_20161118-B https://cdn.slidesharecdn.com/ss_thumbnails/d5116a55-73e2-4061-915a-97150ddd4667-160104084746-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/the-good-the-bad-and-the-ugly-final/56641088 The good the bad and t... https://cdn.slidesharecdn.com/ss_thumbnails/27211af3-0cda-4fc9-a24d-9d01c127e52d-160104084529-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/no-test-without-integration-final/56641037 No Test without Integr...