1. Activity Based techinques fouces on how you test
   1. Scripted Testing
      1. manual testing, done by junior who follow step to step procedure written by senior
   2. Smoke Testing
      1. side effect of regression is done with the goal of proving new build in not worth testing
   3. Exploratory Testing
      1. expect the tester to learn, throughout the project, about the project
   4. Guerilla Testing
      1. fast and vicious attack on the program , senior tester tries out her most powerful attack , if find significant problems the area will be rebudgeted if no problem ignored,
   5. Scenario Testing
      1. test must be realistic,complex(involves several features), easy and quick to tell program is passed or failed, a stakeholder is likely to argue vigorously that the program should be fixed.
   6. Installation testing
      1. installation in various ways and various type of system, verify when uninstall
   7. Load Testing
      1. Load sequence testing
         1. testing done for overnight,days/weeks. goal is discover error that short sequence will miss ex: memory leak, stack overflow
   8. Performance Testing
      1. determine how quickly program run , test to understand optimization needed
   9. Regression testing
      1. involves reuse of the same tests, so you can retest after change goal is to prove that the changed has caused something that used to work to now be broken
2. Function Testing
   1. Decide what kind of testing & bugs looking for
3. Extreme Value Testing
   1. Test for error handling when you enter extreme values into a variables
4. Mutli Dimensional Testing
   1. Cover all the potential problems
5. Beta Testing
   1. have external representative of your market to test software
6. Evaluation based techniques fouces on how to tell whether test is passed or failed
   1. Self verifing data
      1. Data files you use in test carry information helps to determine whether data is corrupt
   2. Comparison with saved results
      1. regression testing in which help to compare to determine test got today from last week
   3. Comparision with specification
      1. a mismatch with a specification
   4. Heuristics Consistency
      1. Consistency with history
      2. Consistency with Image
      3. Consistency with comparable products
      4. Consistency with claims
      5. Consistency with user expectation
      6. Consistency within products
      7. Consistency within purpose
   5. Oracle based Testing
      1. helps us to evaluate whether the program is passed or failed.
7. People Based Testing
   1. User Testing
      1. Testing for who user our product
   2. Alpha Testing
      1. In house test performed by test team
   3. Beta Testing
      1. Design Beta
         1. which ask the SME to appraise the design, should go out as soon as possible
      2. Market Beta
         1. Intended to assure large customer should buy/Install product when released
      3. Compatibilty Beta
         1. Customer who use the product on hardware and software , tester do the same testing and ensure
   4. Eat Your Own Dog food
      1. Company uses and relies on prerelase version of its own s/w and wait until relaible enough
   5. Paried Testing
      1. Two tester work togther to find bugs
   6. Bug Bashes
      1. Testing using secretaries, programmers, marketers,and anyone, done when software is ready to release
   7. SME testing
      1. Give the product to expert on some issue addressed by the s/w and request feedback
   8. Feature of function Integration Testing
      1. Test several fuction togther
   9. Domain Testing
      1. Will analyze a variable and based on that analysis,run test that involve this variable on each function with this variable as an input or an output.
   10. Menu Tour
       1. Walk through all the menu and dialogs in a GUI
   11. Eqv class analysis
       1. Class is a set of values for a variable that you consider equivalent, - Test cases doing same thing, - one of them find catchy bug
   12. Boundary Value
       1. EQV is a set of values, if map you will find either largest & smallest, just a small number than a smallest class number
   13. Best Represntative Testing
       1. A best representative of an eqv class is a least likely as any other value in the class to expose an error in the software.
   14. Input Field and catalog Matrices
       1. depend of input field devlop a test cases and reuse it for similar field
   15. Map and test all the to Edit a field
       1. often can change the value in several ways, copy, entering the value, edit the value
   16. Logic testing
       1. Age < 50 attempt to check every logical relationship in the program
   17. State Based Testing
       1. Program moves from states to states, valid, ignored, rejected.
   18. Path testing
       1. Basis Path testing
          1. Basis path testing involves most or all subpaths of a certain type
   19. Statement and branch coverage
       1. 100 % stmt coverage if you test excute every stmt( line of code) in the program.
   20. Configuration Coverage
       1. measure the percentage of config test that you have run
   21. Specification Based testing
       1. every factual claim that is made about product in the specification, manual,market docs,ads
   22. Requirement based testing
       1. testing based on proving that progrma satisfies every requirement doc
   23. Combination Testing
       1. two or more variable in combination with each other
8. People Based techniques on only why you are testing
   1. Risk based testing
      1. determine what to test next, determine the some of feature program will fail 2nd : determing how it can fail * timing , test data. comparable products
   2. Input Constraint
      1. a constraint is a limit on what the program can handle, if there is no protection for max and min char the program will fail
   3. Output Constraint
      1. when input is legal and output values that the program could handle, display print save
   4. Storageable Constraint
      1. input,output ,calculation are leagal, but operation run the program out of mem yeild data files
   5. Computational Constraint
      1. input & output is fine,course of calculating a value the program fails.
9. Classification of techniques depend on how you think about it
   1. Interaction with muntiple hardware
      1. How to intreact with muntiple hardware
   2. Non functional testing
      1. Non functional testing like performance, security, load, stress
   3. Test data
      1. Test data - like input , ouput, calculation,storage