Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
40 Cards in this Set
- Front
- Back
|
The process for acceptance of software upgrades is primarily covered under which three IT infrastructure library service support functions?
A. configuration management, change management and release management B. change management, configuratioin management and incident maangement C. configuration management, release management and incident management D. incident management, change management and release management |
A. Within the IT infrastructure library, the activities of configuration management maintain information on the IT infrastructure; release management processes handle testing and release acceptance; and change management approves or rejects requests for change and ensures there is adequate testing of the release.
Incident management is primarily a production function to react to actual or potential disturbances in IT services. Incident management activities are normally production versus testing activities. |
|
|
A healthcare organization's pharmacy IT vendor has advised its clients of an urgent patch required to fix a medication administration defect identified by an end-user. Which of the following strategies should the organization follow?
A. package release B. full release C. delta release D. provisional release |
C. A delta release only includes changed hardware and software components. It normally relates to an emergency or temporary fix. A full release includes all components of a release that are built, tested and distributed in entirety. A package release is a combination or bundle of full and/or delta releases of related applications and infrastructure.
|
|
|
The director of applications has advised the laboratory IS manager that a minor upgrade to the laboratory system must be installed, tested and released to production within 30 days to coincide with a radiology system implementation. Which of the following testing priorities should the manager focus on FIRST?
A. unit and system B. functional and unit C. regression and system D. functional and regression |
D. Since time is limited, a risk assessment would be needed to determine the level(s) of testing coverage. A functional test of the upgrade changes would verify that the process changes perform acceptably within the current IT infrastructure. A regression test would assure that the new code did not reverse functionality in the current production release. Unit testing would not verify functional changes - and presumably, the vendor performed unit testing vefore releasing the upgrade. System testing would most likely not meet the 30-day turnaround time.
|
|
|
The CIO has charged the directors of applications and technical services with developing a standard for the appropriate migration of all major software upgrades through the organization's non-production environments. Which of the following testing processes would most likely need modification?
A. procedures B. strategy C. plan D. scope |
B. The testing strategy would be the most logical area to define an overall testing approach based on release levels, as this process would normally need approval IT governance. Testing plans, scope and procedures would normally be defined for the detailed planning of an environmental migratino for a specific release.
|
|
|
In which of the following areas of testing are automated testing tools used most frequently?
A. integration and system B. system and performance C. regression and performance D. regression and integration |
C. Automated tools are most effective for repetitve testing and when limited changes to scrips are needed between testing events. Systems and integration testing typically involve the use of test cases targeted to the functionality changes being implemented, and thus, would require change with each software upgrade or system configuration. Regression testing validates current functionality and may be an efficient use as it would be applicable to multiple releases and would have fewer changes than other types of testing. Performance testing involves simulating a high-intensity of usage, which can be accomplished relatively easily with scripting and other automated tools.
|
|
|
When developing an IT department's testing methodology, what is the primary purpose of testing?
A. obtaining end-user acceptance of the system B. ensuring testing coverage of all system functionality C. detecting errors D. ensuring data and process integrity |
C. detecting errors
The primary purpose of testing is to detect errors and unexpected outcomes. The other answers are all procedures within the testing strategy to achieve this purpose. Ensuring full test coverage enhances the probability of detecting errors across the full spectrum of system functionality. Controlling data and process integrity ensures that testing outcomes are valid. Obtaining user acceptance provides a level of confidence that all key functional errors have been detected and resolved. |
|
|
When time is limited to test a configuration change, which of the following testing levels is MOST appropriate?
A. integration, system and performance B. functional, integration and system C. unit, system and performance D. functional, system and acceptance |
A. integration, system and performance
Performance testing is a key element of the client-server environment as minor configuration changes can have a profound negative impact on system performance. Integration testing would verify that interfaces and integration touch points (sensitive to configuration changes) work correctly. Functional and unit testing would be less impacted by a system configuration change. |
|
|
The primary goal of regression testing is to identify
A. failures across interfaces and touch points between various applications. B. degradation of system performance under increased transactional load C. functional characteristics of a new feature D. gaps between the new and previous versions of software. |
D. gaps between the new and previous versions of the software
Failures across interfaces and touch points would be a goal of integration testing. Degradation of system performance under increased transactional load would be a goal of performance testing. Functional characteristics would be a goal of functional testing. By definition, regression testing evaluates differences between new and previous versions of software. |
|
|
After a review of the test plan for a major release of new code, the director of applications has asked that the plan include more test cases with unexpected or invalid inputs. What type of functional testing is the director referring to?
A. output forcing B. robustness C. normal case D. black box |
B. robustness
Output forcing would be a request to test all possible inputs to force all possible outputs. Thus, output forcing is not targeted to unexpected or invalid inputs. Normal case would be requesting additional cases with expected valid inputs. Black box testing is a general term for testing where testers do not know all the underlying code and relational interactions of the tables. It could apply to all of the test cases and scenarios. Robustness is a request to verify that the system behaves correctly when given unexpected or invalid inputs. |
|
|
Which of the following controls would normally not be a control for system testing?
A. versioning B. quality C. privacy D. change |
C. privacy
Versioning control is the process of assigning unique version names or numbers to various states or releases of system software across testing environments. Quality controls are used to monitor the testing process and identify areas for process improvement. Change control ensures that defect resolution activities, such as code and system configuration updates in the test environment are tested as needed. Privacy controls would normally apply to the access of patient data within the production environment and not specifically during non-production system testing. |
|
|
What are the five common components of testing methodologies?
|
1. Planning
2. Development 3. Execution 4. Reporting 5. Evaluation |
|
|
Define a Delta Release
|
A Delta Release is defined as a partial, emergency or temporary fix.
|
|
|
Define a Full Release
|
A Full Release includes all componenets of the software that have been buildt, tested and distributed in their entirety.
|
|
|
Define a Package Release
|
A Package Release is a bundle of Full and/or Delta Releases as well as their related applications and infrastructure
|
|
|
Define unit testing
|
Testing of one component or module of a system for testing.
|
|
|
Define functional testing
|
Functional testing validates functionality against design specifications. It verifies that the program or system accomplishes its intended purpose
|
|
|
Define integration and interoperability testing
|
Integration and interoperability testing identifies defects in the interfaces and integration points within and between other applications and systems.
|
|
|
Define system testing
|
System testing verfies the functional integrity of a completely integrated system. Testing is conducted on a complete, fully integrated system to evaluate that all system requirements are challenged.
|
|
|
Define performance testing
|
Performance testing measures acceptable system response times at both normal and extreme conditions, such as during load and stress circumstances.
|
|
|
What is system configuration?
|
The required hardware and software components
|
|
|
Define regression testing
|
Regression testing determines whether changes in the new release ahve undone functionality in the current production release.
|
|
|
Define acceptance testing
|
Acceptance testing is the final stage in testing that incorporates end-users' acceptance of the system for production use.
|
|
|
What are control requirements?
|
Control requirements should describe the functional interactions within configuration, change and release management processes, as well as general retesting requirements and system access guidelines.
|
|
|
What is the standard for describing key processes in IT service management?
|
ITIL - Information Technology Infrastructure Library
|
|
|
What 5 questions does the test plan answer?
|
1. how will the testing be done?
2. what will be tested? 3. when can it begin? 4. who will do it? 5. how long will it take? |
|
|
What are the four functional types?
|
1. normal case
2. output forcing 3. robustness 4. combination of inputs |
|
|
What is normal case testing?
|
Normal case testing covers testing with expected valid inputs.
|
|
|
What is output forcing?
|
Output forcing requires that all system inputs be selected to force all outputs.
|
|
|
What is robustness testing?
|
Robustness demonstrates that the system behaves correctly when given unexpected of invalid inputs.
|
|
|
What is combination of input testing?
|
Combination of inputs tests multiple functions assembled into a scenario that fully executes business rules. Process flow diagrams and cause-effect graphing would assist in the development of complex combinations of inputs.
|
|
|
What are the five components of a test case?
|
A test case includes an input, action, output, expected result and actual result.
|
|
|
What is a testing scenario?
|
A testing scenario is a collection of test cases arranged in a specific sequence.
|
|
|
When is automated testing the most efficient?
|
Efficiencies are best achieved for repetitive testing events. Normally in regression testing to evaluate that pre-existing functions are unaffected by changes in newer versions or to create a large number of interactions to enhance transactional stress or load on the system during performance testing?
|
|
|
Testing all aspects of software or systems is resource intensive and time consuming. What should be considered to develop testing priorities?
|
A risk analysis can assist in the development of testing priorities and should consider functionality such as most important, most visible, largest safety impace, largest financial impact, most complex and subject to higher error rates
|
|
|
Why are change management processes especially critical during the testing process?
|
Change management processes ensure that resolutions are completed and that appropriate re-testing is accomplished.
|
|
|
What is versioning control?
|
Versioning control is the process of assigning unique version names or numbers to various states or releases of system software.
|
|
|
What is change control?
|
Change control is typicall a well-defined process for IT departments within the production environment.
|
|
|
Why is it important to use change control in test systems during the testing process?
|
Defect resolution and retesting are a direct outcome of testing, and control of the change process is critical to ensuring that previously accepted functions are retested as needed.
|
|
|
What are the two reasons why test access accounts must be configured identically to the appropriate user access profiles in the production environment?
|
1. to test the security profiles themselves
2. systems can respond differently based on user security settings |
|
|
When should a post-implementation review be conducted?
|
The post-implementation review should be completed after a period of live use. It should not be performed while go-live incidents are being dealt with, process glitches are being worked out, or when users are still being trained and getting used to the system's operations.
|
