Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Test Scenarios</strong><br> Test Scenarios are inputs to test cases. Generation of test scenarios usually takes place in a brainstormig session with project stakeholders, who propose scenarios or ask questions about the way in which the architecture will respond to various situations. Scenarios are used to represent stakeholders' interests and quality attribute requirements. Scenarios should cover a range of anticipated uses of (use case scenarios), anticipated changes (growth scenarios), and unanticipated stresses (exploratory scenarios) to the system. </p> <p>A good scenario makes clear what the stimulus is that causes it and what responses are of interest. For example, a use case scenario might be: “Remote user requests a database report via the Web during peak period and receives it within 5 seconds.” A growth scenario might be: “Add a new data server to reduce latency in scenario 1 to 2.5 seconds within 1 person-week,” and a exploratory scenario might be: “Half of the servers go down during normal operation without affecting overall system availability.” Scenarios should be as specific as possible, identifying stimuli, responses, and environment.</p> <p>A scenario described in vague terms such as 'a communication relay node failed' is not really a valid scenario. You need to get (from stakeholders) further details such as the expected operational consequences, the system assets involved, the end-users involved, the potential affects of the scenario on system operation, and the exceptional circumstances that may arise. More details would include which facility or node detects failure, what is the expected automated response to failure (if any), what is the expected manual intervention, which capabilities will be degraded during the outage, and the expected actions taken to return the relay to service.</p> <p>Scenarios are often prioritized in an iteration and first few scenarios are taken for further test case development.</p> <p><strong>Test Cases</strong><br> Test case development usually transforms each of the selected scenarios from a statement and list of bullets into a well-documented test case. The test cases may combine and/or extend the scenarios, add assumptions and clarifications, define issues, and pose relevant questions. <em>Unlike the test scenarios generation activity, the test cases development is an iterative activity in that new test cases are added and old test cases are refined to support a scenario.</em> </p> <p>First you have to define context of a test case. In a test case involving a communication relay node failure, for example, the context of a test case may define:</p> <ul> <li>the operation at the time of failure</li> <li>what happens immediately after, when the system is reacting to the failure</li> <li>degraded operation during the interval when repair is underway</li> <li>restoring the system to normal operation</li> </ul> <p>Once you have context in place, you have to explore and document issues and questions that are implied by context. For example, the issue could be "how failure is detected?". Questions could be "What subsystem detects the failure?", "How long does it take to detect the failure?" and "What happens during this interval?". Other quality issues could be related to security, availability, performance etc.</p> <p>Architects usually review those issues and questions and determine how a system would react to a scenario. They might refine the architecture to help answer the questions. Test cases are refined and new test cases are added. Test case development is considered complete when all answers to questions are documented.</p> <p>Source: <a href="http://www.sei.cmu.edu" rel="nofollow">http://www.sei.cmu.edu</a></p>
    singulars
    1. This table or related slice is empty.
    1. POCould someone please explain the difference between test scenario and test case
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRitesh
    1. USRitesh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCould someone please explain the difference between test scenario and test case
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload