CPT441 Software Quality Assurance & Testing by Sharifah Mashita https://padlet.com/mashita1/CPT441ClassActivity2 Class Activities for CPT441 en-us 2016-03-04 00:46:07 UTC 2025-12-16 09:49:02 UTC hello@padlet.com https://padlet-assets.storage.googleapis.com/portrait/brainstorm.jpg Dr SMSM mashita1 https://padlet.com/mashita1/CPT441ClassActivity2/wish/98940336 Hi all, for the class activity of the day, we are going to explore the process of testing the ATMS, together ;). 

Please sit in a group, in sequence, in accordance to the test life cycle. ]]> 2016-03-04 01:01:09 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/98940336 Group 3A - Test Implementation https://padlet.com/mashita1/CPT441ClassActivity2/wish/98953324
  • Specifying and prioritizing test case.
  • Creating test data and test scenario.
  • Creating test suite.(Test suite is a collection of test cases that are used to test a software program to show that it has some specified set of behaviors. A test suite often contains detailed instructions and information for each collection of test cases on the system configuration to be used during testing. Test suites are used to group similar test cases together.)
  • Preparing test harnesses and possibly writing automated test scripts. (A test harness is a collection of software and test data for testing a program unit by running it under different conditions and monitoring its behavior and outputs.)
  • Verifying test system and test environment has been set up correctly.
  • Verifying completeness of parts to be tested..
    • ]]>     2016-03-04 03:23:04 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/98953324     Group 4 - Evaluation and Report https://padlet.com/mashita1/CPT441ClassActivity2/wish/98953842 Task:
    - Prepare test summary report which contains summary of test activities and final test results
    - Test Summary: 
       1. Simple (for Project Manager) - for lower level test (component testing - testing of each 
           component in an application is done separately) 
       2. Formal (for stakeholders) - for higher level test (integration, system testing) 
    - Compare test result of each execution (each test level) - to ensure enough testing
    - Exit criteria: Requirements which must be met to complete a specific task:
    - all test case have been executed.
            - type of defect - are they critical or not.
    - bug rate decreased - how many bugs  are detected and resolved.]]>     2016-03-04 03:29:54 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/98953842     Group 2 - Test Analysis and Design https://padlet.com/mashita1/CPT441ClassActivity2/wish/98955333 2016-03-04 03:48:34 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/98955333 Test Closure https://padlet.com/mashita1/CPT441ClassActivity2/wish/98955392 2016-03-04 03:49:41 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/98955392 Dr SMSM mashita1 https://padlet.com/mashita1/CPT441ClassActivity2/wish/98969041 Please include any relevant figures etc for the exercise. Thanks]]> 2016-03-04 07:44:32 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/98969041 Dr SMSM mashita1 https://padlet.com/mashita1/CPT441ClassActivity2/wish/99557770 Guys, take all class activities seriously. They are graded.

    As for tomorrow class, let's speak up your findings ya. Thanks.]]>     2016-03-08 02:57:14 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/99557770     Group 1: Test planning https://padlet.com/mashita1/CPT441ClassActivity2/wish/99826961 What is Test Plan?

    Described the scope, approach, objectives, resources, and schedule of a software testing effort. It identifies the items to be tested, items not be tested, who will do the testing, the test approach followed, what will be the pass/fail criteria, training needs for team, the testing schedule etc.

    Test Objective:

     
    • Ensure that the system performs its core functionality in a timely     manner 
    • Ensure that the system performs all core functionality correctly 
     
    Activities:
    ·        Test items
    o   Describe and list down all the test items and its functionality from SRS

    ·        Features to be tested
    o   E.g. Card verification, login authentication, check balance, withdrawal, transfer

    ·        Features not be tested
    o   E.g. Security – only cover functionality
    ·        Identify risk of testing

    o   Risk of testing:
    1. Schedule: Any slips in meeting project  milestones on time.    
    2.  Staffing: Loss of key team members.  At any time someone may get sick or leave the company, this must be taken in  to consideration.    
    3. Bottlenecks: This could be a bottleneck with respect to  an imbalance in engineer experience (others cannot proceed without the  experience of another), or one group such as software waiting on hardware  before it can continue.    
    4. Training: All engineers must have the proper training  in all areas he or she is responsible.    

    ·        Test Approach
    o  Black box testing
    o  Unit testing, Integration testing, Regression testing, user acceptance testing

    ·        Test environment

    Activity/Test                             |   Tool    
    Development Environment     |   Eclipse     
    Configuration Management    |   Subversion, Eclipse    
                                                               Subclipse Plugin    
    Defect Tracking                          |   Mantis    
    Automated Test Scripts            |   Python, Eclipse 
                                                               configurations     

    ·        Item pass/fail criteria

    ·        Suspension criteriaand resumption requirements
    o  (Suspension) Determine when is the testing task should be suspended
    o  (Resumption) Determine when the testing task can be continue

    ·        Test deliverables
    o  Results from testing which are given to stakeholders

      


    ]]>     2016-03-09 00:30:49 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/99826961     Test Execution https://padlet.com/mashita1/CPT441ClassActivity2/wish/99853600 Description 

    Test execution is the process of executing the code and comparing the expected and actual results. Following factors are to be considered for a test execution process: Based on a risk, select a subset of test suite to be executed for this cycle. Assign the test cases in each test suite to testers for execution.

    Main activities 
    1. Prepare testing environments based on the test plan
    2. Validate test environment to make sure the test environment mirrors the production environment as closely as possible.
    3. Validate test script to examine exactly what the test does; to check if correct metrics are being collected, and if the test script design is correctly simulating workload characteristics.
    4. Execute the test: manually or test automation
    5. Compare the actual results and expected result (baseline & benchmarking)
    6. To re-execute the tests that previously failed in order to confirm a fix.
    7. Document all the results

    Work product
    1. test log (document outcome of the test execution and record the identities and versions of the software under tests)]]>     2016-03-09 06:11:10 UTC https://padlet.com/mashita1/CPT441ClassActivity2/wish/99853600