Testing Methodologies Paper

Testing Methodologies Paper

The healthcare and patient care setting face various challenges which need to be mitigated to ensure that patient care activities proceed without many barriers and that the workflow is as expected. Solutions to some of these problems lie in technology, where a specific software can be developed to solve the problem (Bucci et al., 2019). For example, the elimination of emergency department nursing orders that do not belong to the emergency nursing orders needs software to effectively accomplish it. It is worth noting that such software solutions need testing to eliminate possible software failures. Therefore, the purpose of this paper is to explore possible testing methodologies that can validate the functionalities of the proposed solution.

The Purpose of Testing and Testing Strategy

Software testing is one of the most important steps in the software development process, as ignoring it can lead to huge failures and losses. Testing refers to the process undertaken to evaluate and verify that the application or software does what it was designed to do (Spillner& Linz, 2021). Therefore, it helps improve performance, reduce development costs and prevent bugs.  A testing strategy refers to the guideline that needs to be followed to enable the achievement of the test objectives and execute the test methods detailed in the test plan. Test strategy covers risk analysis, test objectives, and competency plans.

The Testing Methodologies

            The testing methodologies refer to approaches applied in testing the application or software to ensure that its performance is as was expected. There are various testing methodologies that can be applied. The testing methodologies are mainly divided into two; functional testing and non-functional testing (Tsui, 2022). Functional testing refers to a test carried out on the application against the business requirements and entails all test types that ensure that every part of the software functions as expected. Functional testing usually entails four types of testing that have to be executed in the order of unit testing, integration testing, system testing, and acceptance testing. Non-functional testing entails performing tests that deal with the software parts’ operational aspects. The non-functional tests are also divided into four types, including performance testing, security testing, usability testing, and compatibility testing.

After a careful evaluation of the types of testing, the most suitable for testing the earlier proposed software is the non-functional testing methods. The software will have to be tested for its performance; how well it operates to accomplish the tasks. The software will also have to face security tests to ensure that it is free from any potential cyber-attacks (Tsui, 2022). The software needs to be used immediately in the emergency department to help eliminate the orders that do not belong to the emergency department; therefore, it will be prudent to test for their usability. The software may also have to be used in conjunction with the existing organizational software; therefore, compatibility testing is key to ensure that the new software integrates well with the old software, if any.

Planning How to Develop a Testing Scenario

            Testing scenarios are important as they make it easier to test and evaluate the systems or software; therefore, it is important to plan how to develop them. Therefore, various strategies to be employed include enumerating possible users, their objectives, and actions, listing possible cases of system abuse, listing the system events and how the software can handle each (Tsui, 2022). The other strategies include listing benefits and creating end-to-end tasks for checking them, and researching similar software already in use and their behavior.

Test Item vs. Test Condition

            Test item and test condition are two terms that are prominently used in software development and testing. Test items refer to the individual elements that need to be tested. In most cases, there are several test items in a test object which is a subsystem or component to be tested (Tsui, 2022). On the other hand, a test condition is an event or an item of a system or a component that can be verified by at least a test case, for example, structural element, quality attribute, feature, transaction, and function.

How the Test Results are Documented and Issues Mitigated

Documentation is a key aspect of software development as it entails collecting every containing the strategy use, progress, metrics, and test results. When these data are combined, they help track future project requirements, control test coverage, and test effort. The results will be documented using a pre-developed standard template (Spillner & Linz, 2021). To enable easier access and usage, all the data related to the test results will be documented in a single location. In addition, the necessary backup will be made to ensure safety and security. The issues detected during testing will be mitigated using various ways. For example, if the issue is not substantially affecting the software, then it will be accepted as it is or assumed. The other strategy is to adjust various aspects or constraints that help in eliminating the issues. The issues can also be monitored or controlled to optimize the functionality of the solution.

Conclusion

            The existence of unwanted orders at the emergency department has been identified to limit the operations within the department. Therefore a software solution was proposed to help mitigate the problem and improve the operations. However, the software needs to undergo software testing to ensure that it will be effective during operations. Therefore, this write-up has explored various aspects of testing.

References

Bucci, S., Schwannauer, M., & Berry, N. (2019). The digital revolution and its impact on mental health care. Psychology and Psychotherapy: Theory, Research and Practice, 92(2), 277-297. https://doi.org/10.1111/papt.12222.

Spillner, A., & Linz, T. (2021). Software Testing Foundations: A Study Guide for the Certified Tester Exam-Foundation Level-ISTQB® Compliant. dpunkt. verlag.

Tsui, F., Karam, O., & Bernal, B. (2022). Essentials of software engineering. Jones & Bartlett Learning.

For this assignment, you will research and learn possible testing methodologies that validate the functionalities of the proposed solution. In 750-1,000 words, address the following:

Discuss the purpose of testing and testing strategy.
Evaluate various testing methodologies and describe which one would best fit your practicum project.
Plan how to develop a testing scenario.
Differentiate the terms “test item” vs. “test condition” in software testing.
Articulate how the test results are documented and issues are mitigated.
You will not include the time it takes to complete this task as part of your practicum hours.

You are required to cite a minimum of three scholarly resources to complete this assignment. Sources must be published within the past 5 years and appropriate for the assignment criteria and health care and health informatics content.

ORDER A PLAGIARISM-FREE PAPER HERE

MY PRACTICUM PROJECT IS TO ELIMINATE ALL ED NURSING ORDERS THAT DO NOT BELONG IN THE ED NURSING ORDERS.

Rubric
collapse Purpose of Testing and Testing Strategy assessment
Purpose of Testing and Testing Strategy
7.7 points
Criteria Description
Purpose of Testing and Testing Strategy

5. Target
7.7 points
A discussion of the purpose of testing and testing strategy is thorough.

4. Acceptable
6.7 points
A discussion of the purpose of testing and testing strategy is detailed.

3. Approaching
6.08 points
A discussion of the purpose of testing and testing strategy is present.

2. Insufficient
5.7 points
A discussion of the purpose of testing and testing strategy is present but lacks details or is incomplete.

1. Unsatisfactory
0 points
A discussion of the purpose of testing and testing strategy is not present.

collapse Testing Methodologies assessment
Testing Methodologies
7.7 points
Criteria Description
Testing Methodologies

5. Target
7.7 points
Evaluation of various testing methodologies is thorough.

4. Acceptable
6.7 points
Evaluation of various testing methodologies is detailed.

3. Approaching
6.08 points
Evaluation of various testing methodologies is present.

2. Insufficient
5.7 points
Evaluation of various testing methodologies is present but lacks details or is incomplete.

1. Unsatisfactory
0 points
Evaluation of various testing methodologies is not present.

collapse Developing a Testing Scenario assessment
Developing a Testing Scenario
7.7 points
Criteria Description
Developing a Testing Scenario

5. Target
7.7 points
An explanation of how to develop a testing scenario is thorough.

4. Acceptable
6.7 points
An explanation of how to develop a testing scenario is detailed.

3. Approaching
6.08 points
An explanation of how to develop a testing scenario is present.

2. Insufficient
5.7 points
An explanation of how to develop a testing scenario is present but lacks details or is incomplete.

1. Unsatisfactory
0 points
An explanation of how to develop a testing scenario is not present.

collapse Test Item and Test Condition in Software Testing assessment
Test Item and Test Condition in Software Testing
7.7 points
Criteria Description
Test Item and Test Condition in Software Testing

5. Target
7.7 points
A differentiation of test item and test condition in software testing is thorough.

4. Acceptable
6.7 points
A differentiation of test item and test condition in software testing is detailed.

3. Approaching
6.08 points
A differentiation of test item and test condition in software testing is present.

2. Insufficient
5.7 points
A differentiation of test item and test condition in software testing is present but lacks details or is incomplete.

1. Unsatisfactory
0 points
A differentiation of test item and test condition in software testing is not present.

collapse Documenting Test Results and Mitigating Issues assessment
Documenting Test Results and Mitigating Issues
7.7 points
Criteria Description
Documenting Test Results and Mitigating Issues

5. Target
7.7 points
A discussion of how the test results can be documented and issues mitigated is thorough.

4. Acceptable
6.7 points
A discussion of how the test results can be documented and issues mitigated is detailed.

3. Approaching
6.08 points
A discussion of how the test results can be documented and issues mitigated is present.

2. Insufficient
5.7 points
A discussion of how the test results can be documented and issues mitigated is present but lacks details or is incomplete.

1. Unsatisfactory
0 points
A discussion of how the test results can be documented and issues mitigated is not present.

collapse Thesis, Position, or Purpose assessment
Thesis, Position, or Purpose
3.85 points
Criteria Description
Communicates reason for writing and demonstrates awareness of audience.

5. Target
3.85 points
The thesis, position, or purpose is persuasively developed throughout and skillfully directed to a specific audience.

4. Acceptable
3.35 points
The thesis, position, or purpose is clearly communicated throughout and clearly directed to a specific audience.

3. Approaching
3.04 points
The thesis, position, or purpose is adequately developed. An awareness of the appropriate audience is demonstrated.

2. Insufficient
2.85 points
The thesis, position, or purpose is discernable in most aspects but is occasionally weak or unclear. There is limited awareness of the appropriate audience.

1. Unsatisfactory
0 points
The thesis, position, or purpose is not discernible. No awareness of the appropriate audience is evident.

collapse Development, Structure, and Conclusion assessment
Development, Structure, and Conclusion
4.4 points
Criteria Description
Advances position or purpose throughout writing; conclusion aligns to and evolves from development.

5. Target
4.4 points
The thesis, position, or purpose is coherently and cohesively advanced throughout. The progression of ideas is coherent and unified. A convincing and unambiguous conclusion aligns to the development of the purpose.

4. Acceptable
3.83 points
The thesis, position, or purpose is logically advanced throughout. The progression of ideas is coherent and unified. A clear and plausible conclusion aligns to the development of the purpose.

3. Approaching
3.48 points
The thesis, position, or purpose is advanced in most aspects. Ideas clearly build on each other. Conclusion aligns to the development of the purpose.

2. Insufficient
3.26 points
Limited advancement of thesis, position, or purpose is discernable. There are inconsistencies in organization or the relationship of ideas. Conclusion is simplistic and not fully aligned to the development of the purpose.

1. Unsatisfactory
0 points
No advancement of the thesis, position, or purpose is evident. Connections between paragraphs are missing or inappropriate. No conclusion is offered.

collapse Evidence assessment
Evidence
2.75 points
Criteria Description
Selects and integrates evidence to support and advance position/purpose; considers other perspectives.

5. Target
2.75 points
Comprehensive and compelling evidence is included. Multiple other perspectives are integrated effectively.

4. Acceptable
2.39 points
Specific and appropriate evidence is included. Other perspectives are integrated.

3. Approaching
2.17 points
Relevant evidence that includes other perspectives is used.

2. Insufficient
2.04 points
Evidence is used but is insufficient or of limited relevance. Simplistic explanation or integration of other perspectives is present.

1. Unsatisfactory
0 points
Evidence to support the thesis, position, or purpose is absent. The writing relies entirely on the perspective of the writer.

collapse Mechanics of Writing assessment
Mechanics of Writing
2.75 points
Criteria Description
Includes spelling, capitalization, punctuation, grammar, language use, sentence structure, etc.

5. Target
2.75 points
No mechanical errors are present. Skilled control of language choice and sentence structure are used throughout.

4. Acceptable
2.39 points
Few mechanical errors are present. Suitable language choice and sentence structure are used.

3. Approaching
2.17 points
Occasional mechanical errors are present. Language choice is generally appropriate. Varied sentence structure is attempted.

2. Insufficient
2.04 points
Frequent and repetitive mechanical errors are present. Inconsistencies in language choice or sentence structure are recurrent.

1. Unsatisfactory
0 points
Errors in grammar or syntax are pervasive and impede meaning. Incorrect language choice or sentence structure errors are found throughout.

collapse Format/Documentation assessment
Format/Documentation
2.75 points
Criteria Description
Uses appropriate style, such as APA, MLA, etc., for college, subject, and level; documents sources using citations, footnotes, references, bibliography, etc., appropriate to assignment and discipline.

5. Target
2.75 points
No errors in formatting or documentation are present. Selectivity in the use of direct quotations and synthesis of sources is demonstrated.

4. Acceptable
2.39 points
Appropriate format and documentation are used with only minor errors.

3. Approaching
2.17 points
Appropriate format and documentation are used, although there are some obvious errors.

2. Insufficient
2.04 points
Appropriate format is attempted, but some elements are missing. Frequent errors in documentation of sources are evident.

1. Unsatisfactory
0 points
Appropriate format is not used. No documentation of sources is provided.