STE (Final) Microproject
STE (Final) Microproject
5. Resources Required 4
1.Rationale 5
2 4. Literature Review 6
1
Annexure I
3. Proposed Methodology:
In the above project I created, a chart table of test cases. In which I included some attributes like
Test case id, Test case name, Prerequisites, Input data, Steps, Actual result, expected result, Result.
In the Test case id I have given Id to the test report. After the test case name, I have included prerequisites
in which what are required terms of test module is provided. In input data I wrote the input to the test.
Also written some steps about test case name. And then what is the actual result is written. After that
included the expected result. After all the result is pass or fail is given.
The test cases we create are not only the point of reference for the QA phase but also to the UAT.
Internally test cases are Peer-reviewed within the team.
2
When a certain situation is not addressed by a test case – the rule of thumb is, it is not going to get
tested. So, this is a good place to check whether the test suite we created achieves the 100% test
coverage goal or not. To do so, a traceability matrix can be created. Check out all there is to
know about the Traceability matrix here.
Tools – Test management tools like QC, Test help us with the test case creation activity.
For an example of how test cases can be dealt with using Quality Centre, check out this Quality Centre
tutorial.
Automation tools can be used to create test cases- in which case, they are referred to as, Test scripts.
4.Action Plan:
3
5.Resources Required:
Sr.
No. Name of resource / material Specification Quantity Remarks
3 Browser Brave 1
Sr.
No. Enrollment No. Name of Team Member Roll No.
4
Annexure – II
Micro-Project Report
1. Rationale:
In today's software environment writing bug-free code is challenging task, which make software testing
important tool to get the quality software. Testing techniques include the process of executing a program or
application with the intent of finding software bugs and verifying that the software product is fit for use.
Students will learn the way to find bugs by applying types, levels and methods of software testing on
applications with effective test planning approach. It also covers manual testing.
5
4.Literature Review:
Purpose - The purpose of this paper is to review literature on the impact of adoption of ATM technology
from the perspective of customers, banks and suppliers. As per the changing demand of the
customers, in novative software solutions are regularly released. Similarly, banks are deploying
CRM technology to facilitate personalized needs of customers on one-to-one basis. Suppliers of ATMs
are also under pressure to provide ATMs to banks which can meet the latest customer
needs. Design/methodology/approach - This paper is primarily based on a review of literature. Findings –
The articles were categorized under two main themes- Adoption of ATM Technology and Impact of
Adoption of ATM Technology. Impact of ATM Technology is further categorized into three sub
themes- Customer’s Perspectives, Bank’s Perspectives and Supplier’s Perspectives. This study reveals
that there is a dearth of academic literature on Multi-Vendor ATM Technology in developing countries
The ATM Software is to be customized with the help of personalized Technology option so as to
fulfil the needs of multiple cultures in countries like India. Popularizations of biometric and
multilingual ATMs are also required in Rural Areas. Originality/Values – Review on this topic has not
been published in any academic journal to the best of the Author’s knowledge. Keywords: Biometric and
Multi lingual ATMs, CRM Technology, Innovative Software Solutions, Multi-vendor ATM
Technology, Personalized Technology.
6
5.Actual Methodology Followed:
➢ MODULE 1: -
Tc-2 Verify ATM User has Valid Enter user is able to user is able to Pass
Card Account Valid Pin access the bank access the bank
Authentication - account. account.
This test cases is based on the format you can write test cases for
7
➢ MODULE 2: -
Test Case Test Case Preconditions Input Data Expected Actual Status
Id Name Result Result
Tc-3 Verify the Insert the valid Insert the Accept the Card Pass
ATM Card card ATM card accepted
Card
Tc-4 Verify the Card should Enter the Pin is Pin is Pass
card details be inserted pin correct correct
Tc-5 Verify the Card should Enter the Your card your card Pass
expired be entered pin is out of is expired
card date
Tc-6 Verify the Card should Your card your card Pass
disabled be entered is not is not
card -------- working working
This test cases is based on the format you can write test cases for
• Unsupported cards.
• Expired cards.
• Disabled Cards, etc.
8
MODULE 3: -
Test Case Test Case Preconditions Input Data Expected Actual Status
Id Name Result Result
Tc-7 see the ATM card Enter the Showing Showing Pass
account should be pin the account the account
type entered type type
Tc-8 Choose the Pin should be Choose the Account Account Pass
account entered account type is type is
type type select selected
This test cases is based on the format you can write test cases for
9
MODULE 4: -
Test Case Test Case Preconditions Input Data Expected Actual Status
Id Name Result Result
Tc-9 Enter User has a ATM card Showing Pin field Pass
correct valid ATM placed in the pin field Showed
PIN. Debit/Credit the card
Card. reader slot
correctly.
Tc-11 Verify Old pin field Enter the Showing New pin Pass
ATM PIN should be old pin the new pin field
Change showed Pin-1223 field Showed
Tc-12 Verify New pin field Enter the Showing Showing Pass
ATM PIN should be new pin the confirm the confirm
Change showed Pin-6775 and re-enter and re-enter
pin button pin button
10
➢ MODULE 5: -
Test Case Test Case Preconditions Input Data Expected Actual Status
Id Name Result Result
Tc-18 Verify Enter RS: - 3000 Goes on UPI UPI pin Pass
Cardless Amount. pin page showed
ATM Cash password
withdrawal
11
STEPS ON ATM: -
Test Case Test Case Preconditions Input Data Expected Actual Status
Id Name Result Result
Tc-20 Verify Insert ATM Select Cashless Cashless Pass
Cardless card Cashless withdrawal withdrawal
ATM Cash withdrawal Field Field
withdrawal ATM Showing Showed
option.
These Test Cases for Cardless Amount Withdrawal from ATM Machine.
➢ MODULE 6
Test Case Test Case Preconditions Input Data Expected Actual Status
Id Name Result Result
12
DEFECT REPORT
DEFECT REPORT FOR ATM: -
Defect ID D_01
Severity High
Priority High
Status Open
13
6. Actual Resources Used:
3 Browser Brave 1
1. We learn from this project is, how to perform test case for ATM Machine.
2. We learnt to find attributes and modules ATM Machine testing.
3. We learn the use of software testing.
4. We discovered new things while researching the project.
*********
14