You have conducted static analysis on several new modules for an existing product. You are now executing test cases and are seeing inconsistent problems including crashes. Intermittent error messages are appearing.
Despite all your best efforts, you are not able to find reproducible scenarios to force these errors.
What problem in the code are you likely seeing?

• A. Instrumented code
• B. Poor error handling
• C. Wild pointers
• D. Undefined variables

Subject to testing is a software system (COTS) for Project Administration and Control (PACS). PACS is a multi-project system for controlling the project time, e.g., in terms of scheduling and tracking, and managing the productivity of projects, e.g., in terms of effort and deliverables.
During various interviews with stakeholders the following information was gathered:
* Using PACS is not business critical. There is no impact such as high financial losses or problems to the operational continuity of an organization. Its application is not critical since the software package does not support directly the operational, or the primary, business processes of an organization. It supports (project) management in the project planning and tracking process. Of course, it will be highly annoying for users if the system "goes down" from time to time. Although this does not have a high impact for the business process as a whole, the Mean Time Between Failures (MTBF) still needs to be at a good level to be successful in the market.
* Users of PACS typically have an academic educational level, but have no prior experience with this particular type of project management software. The system will be used by a large number of users within an organization.
* The system will be used on a regular basis, e.g., several times per day by project managers and several times per week by project employees. This means that the system will not be used very intensively, often only for some data input or an information request. Its usage is not considered to be very time-critical.
* The data is recorded on-line and real-time. The system is expected to run in multiple hardware environments in various network environments. It is also expected that changes in the operational environments will happen in the upcoming period that also need to be supported.
Based on the information provided by the stakeholder, which combination of non-functional quality characteristics should you propose to test as part of your test approach?

• A. Reliability and Portability
• B. Reliability and Performance efficiency
• C. Performance efficiency and Portability
• D. Security and Reliability

Which statement correctly describes continuous testing'
SELECT ONE OPTION

• A. Each new build of the system triggers a pre-defined set of tests to be executed automatically.
• B. Each new build of the system triggers deployment into a testing environment.
• C. Each modification made to the system is automatically tested and then automatically made implemented in live
• D. Each modification made to the system triggers the tests that cover that change to be executed automatically.

Which statement about test automation being applied to a reactive test approach, is CORRECT' SELECT ONE OPTION

• A. For projects that must comply with externally defined regulations, the automated tests and their results must be traceable back to requirements
• B. An increase in automated test coverage can lead to a greater degree of exploratory testing addressing high risk areas
• C. Automation of test execution in exploratory test sessions can lead to increased efficiency and wider coverage of user stories
• D. BDD can be used within a reactive testing approach by producing automated tests in parallel with the implementation of the user story