際際滷shows by User: marc.rambert / http://www.slideshare.net/images/logo.gif 際際滷shows by User: marc.rambert / Mon, 18 Mar 2013 09:59:44 GMT 際際滷Share feed for 際際滷shows by User: marc.rambert Swiss Testing Day 2013 - How to avoid the testing swiss cheese syndrome /slideshow/swiss-testing-day-2013-how-to-avoid-the-testing-swiss-cheese-syndrome/17320731 marcrambert-std2013-howtoavoidthetestingswisscheesesyndrome-v1-pub-130318095944-phpapp01
As a lot of teams suffer all over the world from the Testing Swiss Cheese Syndrome so I believe it is time to share the information that we have collected. By the end of this presentation, you should be able to make a first diagnostic on your testing activities and reflect on adapted medication. To introduce you to this syndrome, lets think about all the testing activities going on during an application development. It is usually a subset of unit testing, integration testing, functional testing, automated testing, manual testing, exploratory testing, etc. It is very unlikely that a single testing activity covers the whole application. Thats where the similarity with a slide of Swiss cheese: you can imagine holes in your test coverage, areas that havent been covered by one testing activity. The Swiss Cheese Syndrome appends when you dont have an aggregated view of all these testing activities. In such a case, testing holes join their force to create tunnels where bugs and regressions can stay hidden until production. ]]>
As a lot of teams suffer all over the world from the Testing Swiss Cheese Syndrome so I believe it is time to share the information that we have collected. By the end of this presentation, you should be able to make a first diagnostic on your testing activities and reflect on adapted medication. To introduce you to this syndrome, lets think about all the testing activities going on during an application development. It is usually a subset of unit testing, integration testing, functional testing, automated testing, manual testing, exploratory testing, etc. It is very unlikely that a single testing activity covers the whole application. Thats where the similarity with a slide of Swiss cheese: you can imagine holes in your test coverage, areas that havent been covered by one testing activity. The Swiss Cheese Syndrome appends when you dont have an aggregated view of all these testing activities. In such a case, testing holes join their force to create tunnels where bugs and regressions can stay hidden until production. ]]> Mon, 18 Mar 2013 09:59:44 GMT /slideshow/swiss-testing-day-2013-how-to-avoid-the-testing-swiss-cheese-syndrome/17320731 marc.rambert@slideshare.net(marc.rambert) Swiss Testing Day 2013 - How to avoid the testing swiss cheese syndrome marc.rambert As a lot of teams suffer all over the world from the Testing Swiss Cheese Syndrome so I believe it is time to share the information that we have collected. By the end of this presentation, you should be able to make a first diagnostic on your testing activities and reflect on adapted medication. To introduce you to this syndrome, lets think about all the testing activities going on during an application development. It is usually a subset of unit testing, integration testing, functional testing, automated testing, manual testing, exploratory testing, etc. It is very unlikely that a single testing activity covers the whole application. Thats where the similarity with a slide of Swiss cheese: you can imagine holes in your test coverage, areas that havent been covered by one testing activity. The Swiss Cheese Syndrome appends when you dont have an aggregated view of all these testing activities. In such a case, testing holes join their force to create tunnels where bugs and regressions can stay hidden until production. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/marcrambert-std2013-howtoavoidthetestingswisscheesesyndrome-v1-pub-130318095944-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> As a lot of teams suffer all over the world from the Testing Swiss Cheese Syndrome so I believe it is time to share the information that we have collected. By the end of this presentation, you should be able to make a first diagnostic on your testing activities and reflect on adapted medication. To introduce you to this syndrome, lets think about all the testing activities going on during an application development. It is usually a subset of unit testing, integration testing, functional testing, automated testing, manual testing, exploratory testing, etc. It is very unlikely that a single testing activity covers the whole application. Thats where the similarity with a slide of Swiss cheese: you can imagine holes in your test coverage, areas that havent been covered by one testing activity. The Swiss Cheese Syndrome appends when you dont have an aggregated view of all these testing activities. In such a case, testing holes join their force to create tunnels where bugs and regressions can stay hidden until production.
Swiss Testing Day 2013 - How to avoid the testing swiss cheese syndrome from marc.rambert
]]> 785 4 https://cdn.slidesharecdn.com/ss_thumbnails/marcrambert-std2013-howtoavoidthetestingswisscheesesyndrome-v1-pub-130318095944-phpapp01-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 https://public.slidesharecdn.com/v2/images/profile-picture.png