1. Complexity Tour
   1. What are the most complex aspects of the application?
      1. Along with features, consider challenging data sets.
      2. Find the five (N) most complex tasks or aspects of the application.
2. Configuration tour
   1. What program settings can you change?
   2. Which will persist if you exit the program and reopen it?
   3. What operating system settings will affect application performance?
3. Life History tour
   1. Consider an object in the system.( We are considering banking)
      1. When and how can the program create it?
      2. How can the program change it?
      3. How is it used?
      4. What does it interact with?
      5. When does the program deactivate, discard or destroy it?
      6. After the object is terminated, is any record kept of it, for future reference?
4. Compatibilty Tour
   1. What devices should your program work with?
   2. What platforms (operating system and other system software) should your program run on?
5. User Tour
   1. What would users do with this program?
      1. Imagine five different types of users of this application.
         1. Children( below 18
         2. Adult
         3. old people ( above 55)
         4. Adult ( technical)
         5. Adult ( Non - technical)
      2. What would they do with it?
      3. What information would they want from it?
      4. How would they expect its features to work?
6. Interoperabilty Tour
   1. What does this application interact with?
      1. Find every aspect of this application that communicates with other software
      2. "Communication" includes any aspect of the application that creates data that other software will use or reads data saved by other software.
7. Market Context tour
   1. What is the market context for this product?
      1. Who are the competitors?
      2. Among the competitors, are therecheaper ones? Less capable ones? More capable?More expensive?
      3. Why would someone buy this one instead of the other ones? Why would they buy the other ones?
8. Function
   1. Feature
   2. Command
   3. Capabilties
9. Feature tour
   1. Same Function tour/ Same people do a sub - tours.
   2. Find out what program do, what all function do, features, controls, command, line options.
   3. Menu & Window Tour
      1. Find out all the menu (main & context) menu items, windows, Toolbars, icons and other control.
   4. Mouse & Keyboard Tour
      1. Find out all the things can do with mouse & keyboard, Click everything,(F enter,tab, backspace,Esc & Combinations with CTRL+SHIFT+ALT
10. Transcation Tour
    1. A complete task is known as transcation tour
    2. Typically involves sequences of many function
    3. Thin line between transaction and features - Depend on the mindset of tester
11. Error message tour
    1. List every error message, Ask programmer for a list and look for a text file that stores program string.
    2. Highlight a cases that should yeild error message and not
12. Variable Tour
    1. What can you change in the application
       1. - Anything you can change is a variable. Find them all.
       2. - What values can each variable take?
       3. - What are the variables' subranges and subrange-boundaries?
       4. - Some variables (such as many variables that are set with check boxes) enable, disable or constrain the values of other variables. What changes in one variable will cause changes in other variables?
13. Data Tour
    1. What are the data elements of the application?
       1. Some of these are variables
       2. Others might be constants, or information the program reads from disk or obtains from other applications.
    2. Sample data tour
       1. What sample are avialable
          1. Consider data from using or testing a previous version of this application, or an application that should interoperate with this one.
          2. One caution: How will you determine whether the program handles these data correctly?
14. File Tour
    1. What files are used by this program and where are they?
       1. What's in the folder where the program's .EXE file is found? what other folders contain application data ? Check out your system's directory structure, including folders that might be available only to the system administrator.
       2. Look for READMEs, help files, log files,installation scripts, .cfg, .ini, .rc files. Look at the names of .DLLs, and extrapolate on the functions that they might contain or the ways in which their absence might undermine the application.
15. Structure Tour
    1. What is included in the complete product
       1. Code
       2. Data
       3. Interfaces
       4. Document
       5. Hardware
          1. Cables
          2. Security devices required for access
       6. Packaging
       7. Associated web sites or online services
       8. Anything you can test…
16. Operational Modes tour
    1. An operational mode is a formal characterization of the status of one or more internal data objects that affect system behavior.
       1. black-box state-model based testing, an operational mode is a visible state of the program.
       2. Identifying all the operational modes (states) is one of the core tasks of state-model based testing, followed by identifying the transitions
17. Sequence Tour
    1. A sequence (or a subpath) is a set of actions that take you from one state to another.
18. Claim tour
    1. What claims does the vendor make about the product?
       1. Find published claims in manuals, help,tutorials, and advertisements.
       2. Find unpublished claims in internal specifications and memos that make promises or define the product's intent.
19. Benifit Tour
    1. What are the benefits of this application?
       1. Your task is not to find bugs; it is to discover what the program will provide and check whether its fully working
       2. You can communicate much more effectively about a product if you understand what it should be good for.
20. Testabilty Tour
    1. What support for testing is built into this application?
       1. Find all the features you can use as testability features.
       2. Identify available tools that can help in your testing.
21. Specified Risk Tour
    1. Build a catalog of risks.
    2. Imagine a way that the program could fail and then search for all parts of the program that might fail this way.
    3. walk through the program asking, at each point, "what could go wrong here"?
22. Extreme Value Tour
    1. What might cause problems for your variables?
       1. Zero is usually interesting.
       2. Try small numbers where large ones are expected; negatives where positive ones are expected; huge ones where modestly-sized ones are expected; non-numbers where numbers are expected; and empty values where data is expected.
       3. Try potentially unexpected units, formats, or data types.