The objective of this project is to develop a Test Plan and a Functional Test Specification based on a Software Requirements Specification (SRS) of the software product. The goal is to adequately test the implementation provided to reveal as many defects as you can.

Description:

The purpose of this system is to provide a simple and fun experience to the players. It is designed to let players bet money from their balance to give the experience of risk. This is something that experienced blackjack players might look forward to. At the same time, this system is not punishing for less experienced players. When a player looses all the money, the game still lets you start over and play with a basic amount of money. While simple, this Video Blackjack game has a high-score functionality which provides an incentive to the players to compete. Consequently, that would extend the life of the game and add more to the overall experience.

For this project, you are given the source code of the software system to be tested.

The work on the Testing Project will be on phases detailed as follows:

Phase One – Test Plan [10%]:

1- A Testing Plan for adequately testing the product. Use the test plan template and check list provided.

2- To make sure that you understand the code, you are required to draw a Class and an Sequence diagrams for the selected game. You are also required to create a list of requirements that you think are important for that game.

Phase Two - Test Cases [5%]:

2- A Test Specification for Functional Test, which consists of a list of specifications of test cases. Each test case specification should include the following:

- Name/Identifier

- Test items (e.g., the class and method being tested)

- Input specification

- Output specification

- External or environmental conditions (optional)

-Special requirements (optional)

- Dependencies (optional)

You may divide and organize the test case specifications into sections.

3- Discussion

a) How do you divide and partition the SRS for the purpose of testing?

b) What techniques/methods do you use to design the test cases?

The entire deliverable set must be packaged in a single archive file using ZIP or JAR format.

Phase Three - Test Execution [5%]:

Execute the test cases that you designed in Phase Two and make sure to include the following

The Junit/testing code

The integration testing code

The testing report (Pass/Fail) for all created test cases

A Code Coverage Report

Submission:

One team member is required to upload a copy of the solution on Moodle before the specified deadline for each phase:

Phase one is due on: (March 20, 2023).

Phase two is due on: (April 25, 2023).

Phase three is due on: (May 10, 2023).

Project Presentation is due on: (TBD).

Deadlines are very strict, and extensions are not allowed.

With each phase, prepare a detailed report that specifies task distribution and contribution of each team member.

Phases Expectations:

Phase one

A logical list of important functional and non-functional requirements

Complete Class and an Sequence diagrams that reflects the current classes and activities of the system

A well-written introduction that provides a clear description of the aim of the document and the topics that will be covered in the document

Identify and describe the features to be tested and the features not to be tested

Test Types are reasonably identified with consideration to system type and requirements.

Identify and describe risks and rational mitigations

Test logistics are clearly and logically identified

A well written Test Objective that clearly describes the aim of the testing process

Both Suspension and Exit criteria are rationally specified

Rationally specify required system and human resources

The test environment required to execute the planed testes is clearly described

Rational scheduling estimation is provided for all testing tasks

Realistic test deliverables are listed

Phase two

Logical well written and consistent with the requirements Unit Test cases.

Logical well written and consistent with the requirements Integration test cases.

Logical well written and consistent with the requirements System (functional) test cases.

Clearly describe the techniques used to create the test cases.

Phase three

Unit test cases are tested correctly and the code is consistent with unit test cases.

Unit test cases and the final evaluation results are included in the report

Integration test cases are tested correctly and the code is consistent with integration test cases.

Integration test cases and the final evaluation results are included in the report

Major functionality of the system is successfully tested. The report should illustrate all testing details clearly and show the result from executing each test case

Coverage reports are available for all test types

Phase four (Presentation)

Demonstrating thorough research of the project

Engaging choice of content from the project

Your contribution in the project

Engaging style and Lessons learned

 

11 Find an equation of the tangent line to f(x) = 2 sec (x) at x = 6 (Express numbers in exact form. Use symbolic notation and fractions where needed. Express equation in terms of y and x, where y is the dependent variable and x is the independent variable.) equation: