You are in the testing phase of a graphic user interface (GUI): a calculator. Ad

Question

You are in the testing phase of a graphic user interface (GUI): a calculator.

Address the following:

Download the calculator executable file and source code file.

Test your calculator's graphic user interface and fix any problems you find.

Clean the interface so it is clearly understandable to everyone and consistent throughout.

Submit the revised file for this calculator.

Submit a 1–2-page Word document that explains the following:

Your testing, verification, and validation methods

All programming and interface problems you found

All programming and interface solutions you implemented

Your description of the software quality of the calculator

Explanation / Answer

Answer:

Test cases for the calculator depends on the type – scientific, simple calculator, financial calculator or some other specific calculator like programmable calculator.

For the sake of simplicity, we are choosing simple calculator for the test cases. You can come up with plenty of test cases in order to test calculator based on the mathamatical computation. However, we are here testing the calculator to see if it is fit for cosumer use. So we have to make sure that it fits for the most obvious tests. If those tests are passed then we can safely assume that product is fit for use.

Basic Operational Tests

Write the test cases based on the following functions and scenarios.

Functionality Test Cases

Advanced Tests on Scientific Calculator

You can add few more tests in the scientific calculator.

Conversion Function Tests

Some of the advanced scientific calculator has the converter option. It does the conversion of angle, length, weight, area, volume, duration, currency, temperature. Make sure you write the test cases for the same.

Financial Calculator Tests

The additional keys for the financial calculator will be as shown in the image. Some calculator has the mode for enabling these keys.

There are hundreds of test cases that we can make based on the operation of single and combination of the keys.

SOFTWARE TESTING LIFE CYCLE (STLC)

Software Testing Life Cycle (STLC) defines the steps/ stages/ phases in testing of software. However, there is no fixed standard STLC in the world and it basically varies as per the following:

Note that the STLC phases mentioned above do not necessarily have to be in the order listed; some phases can sometimes run in parallel (For instance, Test Designing and Test Execution). And, in extreme cases, the phases might also be reversed (For instance, when there is Cursing prior to Testing).

Interestingly, no matter how well-defined a Software Testing Life Cycle you have in your project or organization, there are chances that you will invariably witness the following widely-popular cycle:

In this type of STLC, you skip phases like design review, test planning, etc – in the hope that the skipping will save you some time and/or cost [But, it never does].

Test Scenarios of Calculator

Validation for Calculator

In ASP.NET, Qforms will go through a validation process just before it executes any Server-based actions, if needed. If the Control that triggers the ServerAction has its CausesValidation property set to "true", then before executing the ServerAction, the Form will go through every visible control in the entire Form and call Validate(). Only after ensuring that every control is valid, will the Form go ahead and execute the assigned ServerAction. Otherwise, every Control that had itsValidate() fail will have its ValidationError property set with the appropriate error message.

What the validation checks for is dependent on the control you are using. In general, QControls that have their Required property set to "true" will check to ensure that data was at least entered or selected. Some controls have additional rules. For example, we'll use QIntegerTextBox here to have Qforms ensure that the data entered in our two textboxes are valid integers.

So we will utilize the QForm's validation in our application by doing the following:

For more advanced users, note that CausesValidation can also be set toQCausesValidation::SiblingsAndChildren or QCausesValidation::SiblingsOnly. This functionality is geared for developers who are creating more complex QFormswith child controls (either dynamically created, via custom composite controls, custom QPanels, etc.), and allows for more finely-tuned direction as to specify a specific subset of controls that should be validated, instead of validating against all controls on the form.

Phase Activity Deliverables Necessity Requirements/ Design Review You review the software requirements/ design (Well, if they exist.)

• ‘Review Defect’ Reports

Curiosity Test Planning Once you have gathered a general idea of what needs to be tested, you ‘plan’ for the tests.

• Test Plan
• Test Estimation
• Test Schedule

Farsightedness Test Designing You design/ detail your tests on the basis of detailed requirements/design of the software (sometimes, on the basis of your imagination).

• Test Cases / Test Scripts/Test Data
• Requirements Traceability Matrix

Creativity Test Environment Setup You setup the test environment (server/ client/ network, etc) with the goal of replicating the end-users’ environment.

• Test Environment

Rich company Test Execution You execute your Test Cases/ Scripts in the Test Environment to see whether they pass.

• Test Results (Incremental)
• Defect Reports

Patience Test Reporting You prepare various reports for various stakeholders.

• Test Results (Final)
• Test/ Defect Metrics
• Test Closure Report
• Who Worked Late & on Weekends (WWLW) Report [Depending on how fussy your Management is]

Diplomacy

Related Questions

Navigate

• Browse (All)
• Browse Y
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.