Question 1: Functional and non-functional requirements are tested to ensure no data is lost if hardware fails
Fantastic news! We've Found the answer you've been seeking!
Question:
Question 1: Functional and non-functional requirements are tested
- to ensure no data is lost if hardware fails
- to ensure the users know how the software works incorrect
- to adhere to audit and legal requirements
- to prove the software will be profitable
- to deliver the best possible quality given the time, resources and scope constraints
Question 2: Bugs will always exist in software because
- future changes in hardware and operating systems will expose new faults
- developers need to interpret specifications and always make mistakes in their coding
- the testers do not test all functions because of time and cost limitations
- the users do not test all of the functions with all combinations of data in UAT
- there are too many variables in business processes, computer software, hardware and the operating systems for all bugs to be found
Question 3: Test cycles are used to
- manage test resources across different projects
- spread testing across a timeframe to match resources and to balance tests over time
- to facilitate the use of automated test tools
- to give the developers more time to fix their bugs
- allow to facilitate major and minor software fixes and give the test team time for retesting
Question 4: The FMEA register contains
- all business process documentation and flowcharts
- all changes to the testing scope and their impact on testing
- the schedule for each domain test and references to the detailed tests
- a list of all software functions and features
- all identified risks and a priority that determines the importance of each risk
Question 5: The number of bugs in the final product is determined by
- the cost of finding the bugs and the importance of the product to the business
- the capability of the development manager to have an effective team
- the business processes, application functionality, platform and the development methodology
- the language used and the experience of the development team
- the skill of the test manager and his team to identify all risks and test them adequately
Related Book For
Posted Date: