Use testing techniques to test the classes in the UML class diagram below: 1. St
ID: 3836584 • Letter: U
Question
Use testing techniques to test the classes in the UML class diagram below:
1. State and explain the testing techniques discussed in the class, and
2. List the testing order of the classes in the diagram.
Card Deck +max cards +current number cards +list of Cards Object shufme() +destroy card() Search Card Cards ownership -type searchers: String Card Hand num searchers integer discard() -regions: List of Strings +draw( Magic cards: List of Magic Cards Event cards: List of Event Cards use shad oin Pla r holde 1.3 Event index: Integer Search selection table name of event card: String who can play: String +Currect row: integer status: String Rovs: list of lsts -effects +append row (hex number X) +play event card() +delete row (hex numberX) +discard event card() Magic +distribute magic card() discard magic card() use magic card() Magic Ring Carrie +location Selecting new. Ringbearer Seize-Ring Check) Remove Ring) Ring CheckD Character Name: String +status: String Combat value +Morale Army morale Endurance Ring weariness Ring rating inventory: list of Magic cards Objects Escape range Capture rating Sorcery rating Location: Hex Object +0ldJocation: Hex object capture flag Spotted-nag +combat() +escape() +use magic cards() +use sorcery() +kil character() +update wounds) +Use ring) +check capture() show attributes) show .combat diffK +check location) +determine combat value() +retreat() +update wounds() +check spotted()Explanation / Answer
Testing Technics are:
Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.
White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.
Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.
Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.
Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.
System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.
End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Sanity testing – Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.
Regression testing – Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.
Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.
Load testing – Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.