Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Testing (Test management (Test planning and estimation (The…

- - - - Software system is very necessary in life.
        
        However, the technological triumph(chiến thắng) has not been perfect.
        
        Some unfortunate individuals and companies have experienced financial loss as a result of defective software.
    - - Why does software fail?
        
        Software engineering remains a human-intensive activity. And humans are fallible beings. So, software is fallible because humans are fallible.
      - When will errors occur?
        
        in code.
        
        in design.
        
        in get requirement.
      - Some kind of fail:
        
        Error(mistake): A human action that produces an incorrect result.
        
        Defect (bug, fault): A flaw in a component or system that can cause the component or system to fail to perform its required function.
        
        Failure: Deviation of the component or system from its expected delivery, service or result.
      - The cost of the defect:
        
        Multiplicative increases in cost.
        
        Phase containment is important because the cost of finding and removing a defect increases each time that defect escapes to a later lifecycle phase.
    - - Where there are defects, there are risks of failure.
        
        While nothing can reduce the level of risk to zero, we certainly can - and should - try reduce risk to an acceptable level prior to releasing the software to customers and users.
    - - we should focus on what tests give us the greatest value by covering the most important parts of the system.
        
        software testing is a way to reduce risks to the quality of the system to an acceptable level
  - - - Implementation:
        
        implement and prioritize the test cases.
        
        Identify and create specific test data which can take the form of inputs,etc
        
        create test suites from the test procedures for efficient test execution.
        
        Verify that the test environment, ideally before test execution starts
      - Execution:
        
        Execute the test procedures manually or with the use of automated test execution tools, according to the planned sequence.
        
        Compare actual results with expected results, observing where the actual and expected results differ. These anomalies should be logged as incidents for further investigation
        
        Log the outcome of test execution.
        
        Report the incidents
        
        repeat test activities when actions are taken to resolve
        discrepancies
- - - - 1. Planning
        
        Defining the review criteria.
        
        Selecting the personnel.
        
        Allocating roles.
        
        Defining the entry and exit criteria for more formal review types (e.g. inspections).
        
        Selecting which parts of documents to review.
        
        Checking entry criteria (for more formal review types).
        2. Kick - off
        
        Distributing documents.
        
        Explaining the objectives, process and documents to the participants.
        3. Preparation
        
        Preparing for the review meeting by reviewing the document(s).
        
        Noting potential defects, questions and comments.
        4. Examination, evaluation, and recording of results (review meeting)
        
        Discussing or logging, with documented results.
        
        Noting defects, making recommendations regarding handling the defects, making decisions about the defects.
        
        Evaluating and recording issues during any physical meetings
        5.Rework
        
        Fixing defects found.
        
        Recording updated status of defects.
        6.Follow up
        
        Checking that defects have been addressed.
        
        Gathering metrics.
        
        Checking exit criteria.
    - - 1.The moderator
        
        leads the review process.
        
        determinesthe type of review, approach and the composition of the review team.
        
        performs the entry check and the follow-up on the rework.
        
        schedules the meeting, disseminates document,stores the data,coaches other team members,paces the meeting, leads possible discussions.
        2.The author
        
        The author is the writer of the document and is responsible for correcting any errors found.
        3.The scribe
        
        The note taker records all issues, issues, and openings during the meeting. Using checklist or viewing related products helps to review more effectively, detect more errors.
        4.The reviewers
        
        Reviewers are individuals who have a technical or professional knowledge, are involved in preparing, identifying and describing errors. Reviewers should be chosen to represent different perspectives and roles in the review process.
        5.The manager
        
        Leaders decide to conduct a review, plan the implementation time in the project plan, determine whether the review objectives are appropriate.
    - - 1.Informal review: test by my self
        2.Walk through group test
        3.Technical review: is a discussion meeting that focuses on achieving consensus about the technical content of a document
        4.Inspection: create a planning to test have to record result (formal)
    - - Find a ‘champion’
        
        Pick things that really count
        
        Pick the right techniques
        
        Explicitly plan and track review activities
        
        Train participants
        
        Manage people issues
        
        Follow the rules but keep it simple
        
        Continuously improve process and tools
        
        Report results
        
        Use testers
        
        Just do it!