测试是一门武功，流程是套路、工具是武器，有简单的花拳秀腿，也有深奥的少林武功！ 测试好比战争，知己知彼，方能百战不殆！ 测试好比破案，精心推断，方能柳暗花明！ 有人说世界不缺少美，而是缺少发现，我看： 其实软件不缺少问题，而是缺少发现！ 以精深的少林武功、用艺术工程的眼光、战争破案的缜密思维去发现软件世界“美”吧！

我的最新日志

  • 天涯社区主页用户注册功能缺陷引发的关于测试的思考

    2008-8-31

    因为工作需要，想在国内最知名的天涯虚拟社区想注册一个用户id发个贴，没有想到登陆 www.tianya.com.cn论坛后点击【用户注册】功能，这个时候系统弹出了一个界面，告诉我是数据来源不明！对应的地址是：http://id.tianya.cn/wrong/wrong.asp?msg=数据来源不明！开始我以为这个是系统的一种安全策略或者跟我特定机器的客户端有问题，但是换了几台机器后发现还是这样，因为急需注册id，所以我先姑且先不管这个是不是一个bug，然后点击了【浏览请进】进入到http://cache.tianya.cn/index.htm 界面，然后点击右上角的【注册】发现系统能进入正常的注册界面：http://id.tianya.cn/user/register/ ，然后我好奇打开另一个ie，输入http://id.tianya.cn/user/register/同样给我提示了一个数据来源不明的信息，只是这次不同的是通过告警框的形式。但是第二次之后就能正常的进入注册界面。当然咯，不管这个是不是问题还是设计者故意这样考虑某种特殊要求，譬如安全？但很显然从常识的角度来看，既然主页上http://www.tianya.com.cn/提供了【用户注册】功能，为什么会弹出如下的出错页面，难道是天涯要拒绝合法用户注册不成？这好像不合逻辑，但即便是这样浏览进去后注册为什么能正常进入注册，难道他们调用的接口不是同一个对象？所以，笔者不得不产生更多的联想？难道天涯这么重要的社区，没有做测试？难道测试工程师的水平竟然会是这样？还是我这样的用户是特殊的不成？

    查看(19) 评论(0)

  • 51深圳第一期开班实况展播

    2008-7-17

    在紧锣密鼓中，51深圳第一期终于在千呼万唤中开展起来，这里先贴几张开班典礼的照片供大家分享！

    第一张：开朗的笑

    第二张：神秘的笑

    更多详细细节请查看这里：http://bbs.51testing.com/thread-120595-1-1.html

    http://bbs.51testing.com/thread-120607-1-1.html

    查看(51) 评论(0)

  • 51testing深圳中心诚聘软件测试专职讲师

    2008-7-10

    不敢说高薪，但是你的付出绝对和你的收获成正比，不敢说有多大发展，但是绝对最有希望成功的一条路

    一、符合以下一种条件：
    1、 熟悉软件开发测试流程，能编写测试计划、设计测试方案、测试用例，有测试管理工作经验优先；
    2、 掌握C/C++或JAVA，掌握SQL Server、Oracle、Mysql中任意一种数据库，有两年以上开发工作经验，掌握Unix或Linux操作系统管理，能够搭建常用的服务；了解软件测试基本概念
    3、 掌握自动化测试理论，熟练使用Robot、QTP、LoadRunner之一种，并有相关自动化测试工作经验一年以上；熟悉计算机软硬件知识，熟悉网络基础知识及TCP/IP协议，熟悉Windows或Unix/Linux操作系统的配置和管理,能够搭建常用的服务；了解J2EE或.net架构
    二、本科及以上学历；
    三、身体状况：健康
    四、素质要求：沟通能力，细心，耐心；思考问题思路清楚，口头表达能力强
    五、有培训经验者优先

    目前急召深圳讲师，简历请发： xulinlin@51testing.com 或请留联系方式

    选择有的时候大于努力

    查看(41) 评论(0)

  • 什么样的用例是好的用例_用例checklist（中英文对照）

    2008-5-15

    Here is a checklist for having well-documented,effective and useful test cases:

    以下是一个如何设计文档化、高效、有用测试用例的检查表（checklist）

    Quality Attributes

    质量属性

    ·                        Accurate: tests what the descrīption says it will test.

    ·                        正确性：确保测试标题描述部分的内容正确性。

    ·                        Economical: has only the steps needed for its purpose.

    ·                        经济性：只为确定需要的目的设计相应的测试步骤。

    ·                        Repeatable, self standing: same results no matter who tests it.

    ·                        可重复性：自我一致性，即不管谁执行此用例，结果一样。

    ·                        Appropriate: for both immediate and future testers.

    ·                        适应性：既能适应短期需要，又能考虑长远需要。

    ·                        Traceable: to a requirement.

    ·                        可追踪性：用例能追踪到一个具体的需求。

    ·                        Self cleaning: returns the test environment to clean state.

    ·                        自我清理性：单个用例不会影响整个测试环境，即用例执行完了可以恢复原有的测                                                       试环境。


    Structure and testability

    结构化和可测试性

    ·                        Has a name and number

    ·                        含有规范的测试标题和编号。

    ·                        Has a stated purpose that includes what requirement is being tested

    ·                        含有一个确定的测试某一个特定需求的目的。

    ·                        Has a descrīption of the method of testing

    ·                        含有关于测试方法的描述。

    ·                        Specifies setup information - environment, data, prerequisite tests, security access

    ·                        指定条件信息-环境、数据、预置的条件测试、安全入口等。

    ·                        Has actions and expected results

    ·                        含有操作步骤和预期结果。

    ·                        States if any proofs, such as reports or screen grabs, need to be saved

    ·                        陈述任何辅助证据，例如截图报告并确保这些东西妥善保存。

    ·                        Leaves the testing environment clean

    ·                        确保测试环境的干净（即用例不会影响整个环境）。

    ·                        Uses active case language

    ·                        描述时使用主动语气结构。

    ·                        Does not exceed 15 steps

    ·                        操作步骤不要超过15步。

    ·                        Matrix does not take longer than 20 minutes to test

    ·                        确保单个用例测试执行时用时不超过20分钟。

    ·                        Automated scrīpt is commented with purpose, inputs, expected results

    ·                        自动化脚本用例添加必要的注释，比如目的、输入和期望结果。

    ·                        Setup offers alternative to prerequisite tests, if possible

    ·                        如果可能，建议提供可选择性的预置条件测试。

    ·                        Is in correct business scenario order with other tests

    ·                        用例之间的先后顺序是否跟业务流程一致，即用例在业务流程中的彼此顺序关系是否合理。


    Configuration management

    配置管理

    ·                        Employs naming and numbering conventions

    ·                        采用命名和编号规范归档。

    ·                        Saved in specified formats, file types

    ·                        保存为特定的格式，文件类型。

    ·                        Is versioned to match software under test

    ·                        用例版本是否与当前被测试软件版本一致（对应）。

    ·                        Includes test objects needed by the case, such as databases

    ·                        包含用例需要的相应测试对象，如特定数据库。

    ·                        Stored as read

    ·                        存档阅读。

    ·                        Stored with controlled access

    ·                        存档时按角色控制访问方式

    ·                        Stored where network backup operates

    ·                        当网络备份时存档。

    ·                        Archived off-site

    ·                        离线归档。

    查看(1095) 评论(0)

  • 献给想改变自己命运的人--最最经典的励志名言

    2008-4-08

    转载“中国教父”--俞敏洪最最经典的励志名言

         人的生活方式有两种，
         第一种方式是像草一样活着，
         你尽管活着，每年还在成长，
         但是你毕竟是一棵草，
         你吸收雨露阳光，
         但是长不大。
         人们可以踩过你，
         但是人们不会因为你的痛苦，而他产生痛苦；
         人们不会因为你被踩了，而来怜悯你，
         因为人们本身就没有看到你。
         所以我们每一个人，
         都应该像树一样的成长，
         即使我们现在什么都不是，
         但是只要你有树的种子，
         即使你被踩到泥土中间，
         你依然能够吸收泥土的养分，
         自己成长起来。
         当你长成参天大树以后，
         遥远的地方，人们就能看到你；
         走近你，你能给人一片绿色。
         活着是美丽的风景，
         死了依然是栋梁之才，
         活着死了都有用。
         这就是我们每一个同学做人的标准和成长的标准。

    查看(211) 评论(0)

  • 面试外企必备_测试英文概念(转载)

    2008-1-23

    A (return to top of page)

    Acceptance Testing: Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

    Accessibility Testing: Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

    Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

    Agile Testing: Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

    Application Binary Interface (ABI): A specification defining requirements for portability of applications in binary forms across defferent system platforms and environments.

    Application Programming Interface (API): A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

    Automated Software Quality (ASQ): The use of software tools, such as automated testing tools, to improve software quality.

    Automated Testing:

    • Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing.
    • The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

    B (return to top of page)

    Backus-Naur Form: A metalanguage used to formally describe the syntax of a language.

    Basic Block: A sequence of one or more consecutive, executable statements containing no branches.

    Basis Path Testing: A white box test case design technique that uses the algorithmic flow of the program to design tests.

    Basis Set: The set of tests derived using basis path testing.

    Baseline: The point at which some deliverable produced during the software engineering process is put under formal change control.

    Benchmark Testing: Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration.

    Beta Testing: Testing of a rerelease of a software product conducted by customers.

    Binary Portability Testing: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

    Black Box Testing: Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

    Bottom Up Testing: An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

    Boundary Testing: Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

    Boundary Value Analysis: In boundary value analysis, test cases are generated using the extremes of the input domaini, e.g. maximum, minimum, just inside/outside boundaries, typical values, and error values. BVA is similar to Equivalence Partitioning but focuses on "corner cases".

    Branch Testing: Testing in which all branches in the program source code are tested at least once.

    Breadth Testing: A test suite that exercises the full functionality of a product but does not test features in detail.

    Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner.

    C (return to top of page)

    CAST: Computer Aided Software Testing.

    Capture/Replay Tool: A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

    CMM: The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

    Cause Effect Graph: A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

    Code Complete: Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

    Code Coverage: An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

    Code Inspection: A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

    Code Walkthrough: A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

    Coding: The generation of source code.

    Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

    Component: A minimal software item for which a separate specification is available.

    Component Testing: See Unit Testing.

    Concurrency Testing: Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

    Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

    Context Driven Testing: The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

    Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

    Cyclomatic Complexity: A measure of the logical complexity of an algorithm, used in white-box testing.

    D (return to top of page)

    Data Dictionary: A database that contains definitions of all data items defined during analysis.

    Data Flow Diagram: A modeling notation that represents a functional decomposition of a system.

    Data Driven Testing: Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

    Debugging: The process of finding and removing the causes of software failures.

    Defect: Nonconformance to requirements or functional / program specification

    Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

    Depth Testing: A test that exercises a feature of a product in full detail.

    Dynamic Testing: Testing software through executing it. See also Static Testing.

    E (return to top of page)

    Emulator: A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

    Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.

    End-to-End testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

    Equivalence Class: A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

    Equivalence Partitioning: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

    Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test.

    F (return to top of page)

    Functional Decomposition: A technique used during planning, analysis and design; creates a functional hierarchy for the software.

    Functional Specification: A document that describes in detail the characteristics of the product with regard to its intended features.

    Functional Testing: See also Black Box Testing.

    • Testing the features and operational behavīor of a product to ensure they correspond to its specifications.
    • Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.

    G (return to top of page)

    Glass Box Testing: A synonym for White Box Testing.

    Gorilla Testing: Testing one particular module,functionality heavily.

    Gray Box Testing: A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.

    H (return to top of page)

    High Order Tests: Black-box tests conducted once the software has been integrated.

    I (return to top of page)

    Independent Test Group (ITG): A group of people whose primary responsibility is software testing,

    Inspection: A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

    Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

    Installation Testing: Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

    J (return to top of page)

    K (return to top of page)

    L (return to top of page)

    Load Testing: See Performance Testing.

    Localization Testing: This term refers to making software specifically designed for a specific locality.

    Loop Testing: A white box testing technique that exercises program loops.

    M (return to top of page)

    Metric: A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

    Monkey Testing: Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

    Mutation Testing: Testing done on the application where bugs are purposely added to it.

    N (return to top of page)

    Negative Testing: Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

    N+1 Testing: A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+1. The cycles are typically repeated until the solution reaches a steady state and there are no errors. See also Regression Testing.

    O (return to top of page)

    P (return to top of page)

    Path Testing: Testing in which all paths in the program source code are tested at least once.

    Performance Testing: Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

    Positive Testing: Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

    Q (return to top of page)

    Quality Assurance: All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

    Quality Audit: A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

    Quality Circle: A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

    Quality Control: The operational techniques and the activities used to fulfill and verify requirements of quality.

    Quality Management: That aspect of the overall management function that determines and implements the quality policy.

    Quality Policy: The overall intentions and direction of an organization as regards quality as formally expressed by top management.

    Quality System: The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

    R (return to top of page)

    Race Condition: A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

    Ramp Testing: Continuously raising an input signal until the system breaks down.

    Recovery Testing: Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

    Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

    Release Candidate: A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

    S (return to top of page)

    Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.

    Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load.

    Security Testing: Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

    Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

    Soak Testing: Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

    Software Requirements Specification: A deliverable that describes all data, functional and behavīoral requirements, all constraints, and all validation requirements for software/

    Software Testing: A set of activities conducted with the intent of finding errors in software.

    Static Analysis: Analysis of a program carried out without executing the program.

    Static Analyzer: A tool that carries out static analysis.

    Static Testing: Analysis of a program carried out without executing the program.

    Storage Testing: Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

    Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

    Structural Testing: Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

    System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

    T (return to top of page)

    Testability: The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

    Testing:

    • The process of exercising software to verify that it satisfies specified requirements and to detect errors.
    • The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829).
    • The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component.

    Test Automation: See Automated Testing.

    Test Bed: An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

    Test Case:

    • Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.
    • A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

    Test Driven Development: Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

    Test Driver: A program or test tool used to execute a tests. Also known as a Test Harness.

    Test Environment: The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

    Test First Design: Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

    Test Harness: A program or test tool used to execute a tests. Also known as a Test Driver.

    Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.

    Test Procedure: A document providing detailed instructions for the execution of one or more test cases.

    Test Scenario: Definition of a set of test cases or test scrīpts and the sequence in which they are to be executed.

    Test scrīpt: Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

    Test Specification: A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

    Test Suite: A collection of tests used to validate the behavīor of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

    Test Tools: Computer programs used in the testing of a system, a component of the system, or its documentation.

    Thread Testing: A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

    Top Down Testing: An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

    Total Quality Management: A company commitment to develop a process that achieves high quality product and customer satisfaction.

    Traceability Matrix: A document showing the relationship between Test Requirements and Test Cases.

    U (return to top of page)

    Usability Testing: Testing the ease with which users can learn and use a product.

    Use Case: The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

    User Acceptance Testing: A formal product evaluation performed by a customer as a condition of purchase.

    Unit Testing: Testing of individual software components.

    V (return to top of page)

    Validation: The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

    Verification: The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

    Volume Testing: Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.

    W (return to top of page)

    Walkthrough: A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.

    White Box Testing: Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing.

    Workflow Testing: scrīpted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.

    X (return to top of page)

    Y (return to top of page)

    Z (return to top of page)

    Have a definition you'd like to see added to this page? Let us know.

    查看(199) 评论(0)

  • 闲谈微软测试峰会----微软IE测试主管

    2008-1-18

    今天听一同事聊到软件测试峰会，据说每天的培训费用高达2400多元，很好奇的就进去看看了。发现了其中的一些视频，挑选了其中一个微软IE测试主管就边界值和等价类的培训。这让我想起了我们的就业培训也讲等价类，也讲边界值、正交分析、因果图、判定表等等各种测试用例的设计方法。因此也希望从中吸取一些精华的东西。但是或许是时间太短，收获太有限了。这让我回想起以前在公司的时候也曾经有幸去跟IBM、微软的高级工程师交流关于性能测试、自动化测试的一些思想、理念、方法与工具。非常报有希望的去，但发现收获很浅，有时也怀疑自己领悟力真的太有限了。后面慢慢发现。原来测试的东西在国内做的好的还真的就那么几家，华为算是测试技术研究投入最大，效果最好的一家吧。所以我也一直跟我的学员强调，测试的知识其实真的就像一座房子，最核心的内容就是测试的方法、方法分为用例的设计方法、测试方案设计的方法（也就是我们通常所说的测试需求的分析方法）。测试的流程、测试的工具。产品的质量、测试的标准和规范。测试的基础知识，比如开发的基本技能、英语、数据库、业务知识等等。基础好比地基、测试的标准和规范好比房屋的标准和规范、测试的方法、流程、工具好比房屋的框架。而测试的项目管理好比房地产的项目管理。涉及到人员、测试资产、设备的管理，管理不外乎流程、方法、和工具。其实测试就是一种生活，一种生活态度，这也就不难理解微软为什么会请家庭主户来进行测试了。而管理最重要的是度量，humphrey教授曾经讲过一句话，没有度量就没有管理。同样我送给大家一句话，（If you don't know where you are, a map won't help.）如果你不知道自己在哪里，地图也帮不了你。以下的链接是对应的视频链接，供大家分享。

    http://www.msup.com.cn/showVideo,20071011-13.aspx

    查看(105) 评论(0)

  • 如何成为伟大的测试工程师-Hallmarks

    2008-1-06

    Hallmarks of a Great Tester

    If you ask me, I'll tell you a great tester

    Is devious

    A great tester has a streak of deviousness.  Anyone can follow the lists of test cases that abundantly fill most books on testing.  A great tester can move beyond these lists and dream up an endless series of gnarly methods for attacking the program.  A great tester is described by developers as "sick" and "demented".

    Is curious

    A great tester is interested by everything.  A great tester wants to understand why everything works that way it does.  The best (or worst, depending on your point of view) bugs are a result of interaction between two pieces of software (applications, modules, components, whatever).  A great tester knows that understanding how something works leads directly to understanding how that something interacts with another something, which interaction leads directly to bugs.  A great tester manifests this curiosity in every aspect of life:  how does marketing work?  How are construction cranes built?  Why do they add rebar to concrete?  How are crayons made?  A great tester's curiosity knows no bounds.

    Is excited by bugs

    A great tester thinks bugs are cool.  A great tester shows up in a developer's office on a regular basis with a big grin eager to show off the latest nifty keen horridly awful bug that the tester found in the developer's code.  A great tester boasts about bugs to other testers and eagerly listens to other testers' exploits.

    Knows there are always more bugs

    A great tester knows that no application is ever bug free.  A great tester knows that an application that seems to be bug free is really full of bugs they haven't thought to look for.  A great tester is always on the lookout for new types of bugs.  A great tester views every bug found by a customer as a sign they missed an entire class of bugs.

    Stays on track

    A great tester knows that finding and isolating bugs to their root cause requires focus.  A great tester doesn't ignore bugs found along the way, but postpones investigating them until the current bug is nailed.  (And, of course, gleefully told to the corresponding developer.  And boasted about to other testers.)

    Scopes appropriately

    A great tester knows that they will not have sufficient time to run every test case they would like to run.  A great tester prioritizes and scopes their tests so that the tests most likely to find the bugs most likely to affect the customer are executed first.

    Investigates weird behavīor

    A great tester watches for odd occurrences.  Icons that display one position off from where they should and radio buttons that don't stay set may be a simple programming error, but a great tester knows that such oddities are just as likely to be but the tip of a nasty bug.  A great tester goes beyond "That's weird but that's life" to "A-ha!  That's what's going on!"

    Writes precise bugs

    A great tester takes the time to narrow a bug down to the minimum number of steps necessary to reproduce a bug.  A great tester tests around a bug to understand what the bug actually is.  A great tester writes bugs that state the bug exactly and clearly distinguish between what is proven fact and what is conjecture on the part of the tester.

    Has passion for the customer

    A great tester knows that they are the last defense against the customer receiving a product that doesn't serve the customer's needs.  A great tester understands every aspect of the customer.  A great tester understands what the customer needs to do and how the customer wants to use the product.  A great tester looks beyond the customer's needs to see how the product can revolutionize the customer's tasks.  A great tester promotes the customer's point of view throughout the product cycle, from the first nascent product vision through specifying and implementing features to cutting features and triaging bugs to product release and ongoing maintenance.  A great tester helps the rest of the product team understand the customer as well as they do.

    Is a specializing generalist

    A great tester is completely familiar with every detail of their feature.  A great tester also understands how their feature fits into and affects the entire product.  A great tester is willing to change or even cut their feature in order to make the product as a who