SOFTWARE TESTING PROCESS KNOWLEDGE EVALUATION
Name:
Date
Result (%)
1. What are the major activities of the testing process:
o Plan,
o Design
o Prepare
o Estimate
o Test
o Delivery
o Execution
2. When planning the testing what factors should be taken in consideration:
o At least two testing sessions
o Before the delivery is made on production all major functionalities should be tested
o Every raised bug should be retested
o Performance
o All testing related document will be stored in the project repository
3. What are the requirements in order for the testing activity to proceed?
o Timetable
o Specification
o Functional support
o Scope of the testing
o Application (location, access, build, access to the issue tracking system and
project repository)
4. What roles are project based roles:
o Team Lead
o Primary Tester
o Tester
5. What are responsibilities of a tester:
o Request and organize meetings
o Review quality of the documents and activities
o Keep track of issues.
o Report task status according to completion
o Execute test cases
o Request new builds on testing environment
6. What are the responsibilities of a primary tester:
o Request and organize meetings
o Review quality of the documents and activities
o Keep track of issues.
o Report task status according to completion
o Execute test cases
o Request new builds on testing environment
7. Who can request estimations:
o Primary Tester
o Business Analyst
o Project Manager
o QA Team lead
8. What activities should be taken into account when estimating the testing effort:
o Standard checks
o Update Test Description
o Create Test Results
o Provide Estimates
o Documentation analysis
o Update existing functionalities testing estimations
9. When estimating the testing of existing functionality you must consider:
o Not all the functional tests have to be conducted
o Available time
o Impact of new development
o Available resources
o Test cases or check lists if they exist
o Tem member estimations
10. When reviewing a speciation you should:
o Send all questions to BA
o Fill in review template
o Provide a rough estimation of how much time will be required
11. When should a test plan be created according to the template:
o When there are a lot of team members
o If the project has a larger consistency
o If the Primary tester and the Project manager decide it is required
o If the project will take a long time
12. What statements are true:
o Once the specifications are understood the writing of tests cases/checks can begin
o The decision of what kind of tests description should be created for the
functionalities to be developed has to be taken by the Primary Tester
o Once the specifications are understood estimations should be provided
o Each standard test description should contain only :numbered steps, action,
expected results
o During the period when test scenarios are developed if more or less time is
required the estimates should be updated and the project manager informed
13. What content rules should you take into consideration when creating a standard tests
description
o Action columns contain the exact action that needs to be performed by the user in
order to get the result from the Expected results column
o The only form (words used) to be used across the whole document is: The user
clicks….executes… etc
o In the Expected results column you should use words such as: view, examine,
notice, etc.
o Each test scenario and test case should contain a unique number
o A test scenario should not contain other test scenarios
14. A check from a light test description can have one of the following statuses:
o Passed
o Reopened
o Failed
o Not tested
o Unavailable
o Not delivered
15. A test session has the following attributes
o Scope
o Results
o Time details
o Project plan
o Versioning in Jira
16. Who can reject a delivery:
o Team lead
o Primary tester
o Tester
o Project Manager
17. When can a delivery be rejected:
o When the only scope is ad hoc tests
o Bugs cannot be retested
o Functionality is not working
o Scope neither clear nor specified
o No resources available
18. What statements are true:
o During the testing period the tests results should be updated on daily bases
o If a defect is uncertain it should be raised as an open issue.
o After a test session is finished a review of the estimates should be done
o The tests description should be updated only if the project manager approves it.
o Once issues are resolved it is mandatory to re-test them
o It is considered a best practice to retest on the final version the blocker, critical and
major issues.
19. In order to create a tests results document for a test description you should follow the
guidelines:
o For each test case a test result line should be available
o Never separate tests for validation and business rules
o For each module a separate test results document should exist
o For each test session a separate sheet should exist.
o Within a test session several build could be available.
o For each build a separate result column should be used
20. What statements are true
o The test results will be communicated to all team members once a test session is
finished or when requested.
o A bug can be reopened if the fix has caused a different problem than the one
stated
o A bug can be raised as a blocker for a functionality that is not working and there is
no workaround
o When an application is newly installed the following tests have to be conducted:
3erd party components, performance, security
o The training plan is should contain only a knowledge presentation of the
functionality or module and exercises that the trainee must do