Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Testing (:moneybag:Strategies (:four:系统测试 (:one:恢复测试 (:explode…

- - - - :explode:发现网页的语法错误,语义错误,内容组织错误
      - :maple_leaf:用户界面处测试,数据转换的地方是不是建立了正确的SQL
    - - :explode:界面的颜色字体什么的是否合格,测试不同浏览器,链接表单什么的测试
      - :one:可用性测试
        
        :explode:测试这个Web是不是可用的,能不能满足用户需求
    - - :explode:测试导航语义和导航链接是否正确
    - - :explode:测试用户输入(表单)后,输出是否和预期一样这一类的功能测试
    - - :one:负载测试(Load Testing)
      - :two:压力测试(Stress Testing)
        
        :moneybag:N(并发用户的数量),T(每单位时间的在线事务数量),D(每次事务服务器处理的数据负载)
- - - - :explode:These are mistakes made by programmer.They exists in the mind and can result in one or more faults in he software
    - - :explode:These consist of incorrect material in the source code, and can be the productof one or more errors. Faults can lead to failures during program execution.
    - - :explode:These are symptoms of a fault, and consist of incorrect, or out-of-specification behavior by the software
  - - - :explode:The Purpose of Verification is to ensure that selected work products meet their specified requirements.
    - - :explode:The Purpose of Validation is to demonstrate that a product or product component fulfills its intended use when placed inits environment.
- - - - :explode:刚好>,=,<最大值/最小值
    - - :explode:以封装好的类为单元进行测试
      - :warning:由于继承性,所以测试基类的操作也要在子类环境中进行
  - - - :one:基于线程测试
        
        :explode:一个线程为单位,把需要的类和数据都弄起来一起测试.最后再回归测试一下
      - :two:基于使用的测试
        
        :explode:先从独立类测试,再不断测试那些会有依赖类的类
    - - :one:自顶向下集成
        
        :frowning:需要桩
      - :two:自底向上集成
      - :moneybag:Smoke Testing
        
        :explode:找到某个有问题的构件,每天用这个构件和系统集成来测试
        
        rolling integration testing
        
        :heavy_dollar_sign:回答是否值得继续测试
  - - - :explode: focuses on user visible actions and outputs from the system
    - - :one:α测试
        
        :explode:开发团队内部测试
      - :two:β测试
        
        :explode:最终用户测试
  - - - :explode:对系统从错误中恢复过来的测试
    - - :explode:测试系统是否能应对非法破坏行为
    - - :link:压力测试
    - - :dagger_knife:fio,iozone,dd,atop,iperf
- - - - :three:Validation Testing
      - :one:Unit Testing
        
        :bread:xUnit
        
        one piece of the functionality
        
        JUnit for Java, RUnit for R, PyUnit, SQLUnit
        
        Test Runner, Test case, Test fixtrues, Test suites
        
        each test should be isolated from others
      - :two:Integration Testing
        
        interactions between different components of a system
        
        drivers and stubs
        
        drivers call the software on the test and pass the test data as input( prepared file, code,etc)
        
        system calls the stubs software
        
        :pineapple:top-down integration
        
        :musical_note:an early outline of the overall program is availabg and it is convinient for testers
        
        :sweat_drops:proper stubs are difficult to design; On adding the lower layer, the upper layers need to be tested again
        
        :recycle:types
        
        :one:top-down
        
        :two:bottom-up
        
        :musical_note:drivers easier to produce than stubs;
        
        :three:sandwich
        
        :explode:hybrid of top-down and bottom-up
        
        considerations
        
        number of drivers and stubs
        
        which layer is available to test first
        
        where is the critical modules in the system
    - - :one:Fault-Based Testing
        
        :explode:测试人员想出可能发生故障的地方,然后进行测试
      - :two:Scenario-Based Test Design
        
        :explode:用户肯定会完成的任务,然后我去测试
        
        :smile:发现和用户的交互错误
    - - :one:Random Testing
        
        :explode:一个类有很多方法,理论上说这些方法都有一个规定的执行顺序.那么我就打乱这些执行顺序,然后随便执行来测试
        
        :smile:不同类实例的生命历史
      - :two:划分测试
        
        :explode:类似于等价类测试,只不过这次是根据改变类的状态的能里进行划分来测试
    - - :one:Multiple Class Testing
        
        :explode:随机
      - :two:Tests Derived from Behavior Models
        
        :key:类的状态
- - - - AF:可选
      - UC
        
        use-case
      - TC
        
        test-case
      - TC对UC的覆盖率要好几千
- - - - :musical_note:good points
        
        :two:改善公司组织文化,提高公司的参与感
        
        :one:高效交付
      - :sweat_drops:dark side
        
        :one: if you only have a few releases a year and velocity is not critical in your organization, DevOps may be simply too expensive and complicated to implement.