Comments on: Test Scenario/Script Template http://www.carnegiequality.com Tools, Tips, and Templates for Quality Software Thu, 19 Jan 2012 19:15:07 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Brad Kuhn http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-12505 Brad Kuhn Fri, 28 Oct 2011 19:40:02 +0000 http://www.carnegiequality.com/?page_id=58#comment-12505 Depends on which test phase you're asking about. This template would be applicable to system/integration or User Acceptance Testing (UAT). During system or integration testing, it is generally the Test team's responsibility to plan, test, and document their own test results. I advocate having the business be involved in the planning phase, and if possible it's great if they can review and provide input on the test scenarios, but I generally haven't seen that happen too much in my experience. For UAT, however - it's the responsibility of business to sign off that the delivered system meets their business objectives and requirements. The business should be heavily involved in planning for UAT. However, test planning is usually not what they do full-time - so don't leave the business to plan in a vacuum. What I have generally seen is that the business often leverages scenarios and scripts used during system test. This will vary from company to company (and maybe even project to project). Depends on which test phase you’re asking about. This template would be applicable to system/integration or User Acceptance Testing (UAT). During system or integration testing, it is generally the Test team’s responsibility to plan, test, and document their own test results. I advocate having the business be involved in the planning phase, and if possible it’s great if they can review and provide input on the test scenarios, but I generally haven’t seen that happen too much in my experience.

For UAT, however – it’s the responsibility of business to sign off that the delivered system meets their business objectives and requirements. The business should be heavily involved in planning for UAT. However, test planning is usually not what they do full-time – so don’t leave the business to plan in a vacuum. What I have generally seen is that the business often leverages scenarios and scripts used during system test. This will vary from company to company (and maybe even project to project).

]]> By: Chad http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-12491 Chad Thu, 27 Oct 2011 20:49:02 +0000 http://www.carnegiequality.com/?page_id=58#comment-12491 Thanks for the great article. Between the business and IT, who should create the test scripts and screen shots for users who will do the testing? Thanks for the great article.

Between the business and IT, who should create the test scripts and screen shots for users who will do the testing?

]]> By: Brad Kuhn http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-12398 Brad Kuhn Tue, 18 Oct 2011 12:23:50 +0000 http://www.carnegiequality.com/?page_id=58#comment-12398 Sorry for the delayed response. Test components are just a way to categorize functional areas or components that are being tested. If it's not applicable to your domain, you should treat this as optional. But frequently, particularly in large software implementation projects, there is a lot of integration of different components/technology. If your test scenario calls out which components are involved in the scenario, then it's easier to get a sense of test coverage and allows for better planning. The example I gave in the post dealt with different components becoming available to test at different times. For example, let's say you are going to test an Order Management project. As your components you might have: 1. Product Selection 2. Quoting/Pricing 3. Order Creation 4. Order Submission/Processing 5. Order Management (e.g. cancellation) If during week 1 of testing Order Submission and Order Management were not available, but the other 3 components were - then you would identify which scenarios deal with just the first three components and start testing those, holding the others until their respective components became available to test. Hope this helps! Sorry for the delayed response. Test components are just a way to categorize functional areas or components that are being tested. If it’s not applicable to your domain, you should treat this as optional. But frequently, particularly in large software implementation projects, there is a lot of integration of different components/technology. If your test scenario calls out which components are involved in the scenario, then it’s easier to get a sense of test coverage and allows for better planning.

The example I gave in the post dealt with different components becoming available to test at different times. For example, let’s say you are going to test an Order Management project. As your components you might have:
1. Product Selection
2. Quoting/Pricing
3. Order Creation
4. Order Submission/Processing
5. Order Management (e.g. cancellation)

If during week 1 of testing Order Submission and Order Management were not available, but the other 3 components were – then you would identify which scenarios deal with just the first three components and start testing those, holding the others until their respective components became available to test.

Hope this helps!

]]> By: neil http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-12363 neil Fri, 14 Oct 2011 14:45:40 +0000 http://www.carnegiequality.com/?page_id=58#comment-12363 Excellent Article. Can you clarify what you mean by Test Components/Requirements though, maybe with an example? Excellent Article.

Can you clarify what you mean by Test Components/Requirements though, maybe with an example?

]]> By: Lhei http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-11442 Lhei Thu, 12 May 2011 06:48:14 +0000 http://www.carnegiequality.com/?page_id=58#comment-11442 Very informative and useful. Thanks! Very informative and useful. Thanks!

]]> By: TerryS http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-10289 TerryS Tue, 09 Nov 2010 15:41:45 +0000 http://www.carnegiequality.com/?page_id=58#comment-10289 First article that came up when I googled "test script template" & it was exactly the info I needed to get started on customizing my own template. Thanks very much. First article that came up when I googled “test script template” & it was exactly the info I needed to get started on customizing my own template. Thanks very much.

]]> By: suresh http://www.carnegiequality.com/testing/test-script-template/comment-page-1/#comment-10025 suresh Mon, 30 Aug 2010 02:39:42 +0000 http://www.carnegiequality.com/?page_id=58#comment-10025 Excellent and easy to understand. Good article. Excellent and easy to understand.
Good article.

]]>