Jira Xray Tests With Test Steps

Tests with Test Steps Generated with the Better Excel Plugin for JIRATue Feb 11 09:43:59 CET
for JIRATue Feb 11 09:43:59 CET 2020
T Key Summary Test Type

Test EBANK-1 Payment request is authenticated
Manualsecurely
Test EBANK-10 Abbreviations are consistently

Manual
used
Test EBANK-11 Confirmations are prompted

Manual
when leaving forms without saving
Page 1
Tests with Test Steps Generated with the Better Excel Plugin for JIRATue Feb 11 09:43:59 CET 2020
Test EBANK-12 Type ahead feature is default

Manual
for form filling
Test EBANK-13 Table scrolling edge cases are

Manual
handled
Test EBANK-14 Insufficient funds notifications

Manual
are straightforward
Page 2
Test EBANK-15 All documented shortcut keys

Manual
can be used
Test EBANK-16 Irrelevant menu items don'tManual

appear
Test EBANK-17 Keyboard switching is automatic

Manualfor number type fields on mobile
Page 3
Test EBANK-18 Loading website with various

Manual
connections quality
Test EBANK-2 Test the behavior of required

Manual
fields for a card-not-present payment transaction
Test EBANK-20 Mobile browser compatibility

Manual
test
Test EBANK-22 Desktop Operating System Manual

compatibility test
Page 4
Test EBANK-23 Response time test at different

Manual
connection speeds
Test EBANK-24 Verify required SSL securityManual

compliance
Test EBANK-25 Database consistency test Manual
Test EBANK-26 HTTP protocol used to storeManual

cookies
Page 5
Test EBANK-3 Enter different data types Manual
Test EBANK-31 Onboarding instructions depend

Manual
on customer account type (Standard)
Test EBANK-4 Use various text field widthsManual
Page 6
Test EBANK-40 Payment verifications performed

Manualfor account balance
Test EBANK-41 New third-party request canManual

be registered on Bank's API platform
Test EBANK-42 TPP list can be accessed by Manual

Bank employees
Test EBANK-5 Behavior of form instructions

Manual
Test EBANK-57 Transfer push notifications Manual

are sent
Page 7
Test EBANK-6 Onboarding instructions depend

Manual
on customer account type (Premium)
Test EBANK-64 Scanned account holder ID Manual

matches selfie
Test EBANK-65 Scanned account holder ID Manual

doesn't match selfie
Test EBANK-7 Financial goal progress bar Manual

visibility on different screens
Page 8
Test EBANK-8 Payment transaction submitted

Manual
multiple times
Test EBANK-9 Language is automatically selected

Manual based on device location
31
Created at 11/Feb/20 9:44 AM by Levente Szabo with Better Excel Exporter for Jira
help »
Page 9
Manual Test Steps

Step 1: Initiate a payment request.
Data: input type="shop_id, transaction_id" name="action"
value="PAYMENT"
Expected Result: User is redirected to the payment page.
Step 2: Select the card type of your choice.

Data: Use official VISA and Mastercard test credentials
Expected Result: Card is selected.
Step 3: Submit the payment transaction.

Expected Result: 3D Secure authentication is performed.
Step 1: Navigate to About screen.

Expected Result: About screen is loaded.
Step 2: Hit CTRL+F to search.

Expected Result: The search box appears.
Step 3: Search for an abbreviation.

Data: FAQ
Expected Result: Results are highlighted and they are consistent.
Step 4: Search for an abbreviation.

Data: LTD
Expected Result: Results are highlighted and they are consistent.
Step 1: Navigate to the Registration screen.

Expected Result: Registration screen is loaded.
Step 2: Fill the Name field.

Data: Sandra Green
Expected Result: Value is accepted.
Step 3: Fill the Phone number field.

Data: 9018746701
Expected Result: The value is not accepted.
Step 4: Fill the Address field.

Data: 3242 Feathers Hooves Drive
Expected Result: The value is accepted.
Step 5: Navigate back to the Home screen.

Expected Result: Warning box appears that filled data will be lost.
Page 10
Step 1: Navigate to the Support screen.

Expected Result: The Support screen is loaded.
Step 2: Edit the Name field.

Data: Chri
Expected Result: List appears with suggestions to Christopher and
Christina.
Step 3: Click name Christina.

Expected Result: Field is filled with Christina.
Step 1: Navigate to the My investments screen.

Expected Result: My investments screen is loaded with investment
items in table form.
Step 2: Scroll down to the bottom of the table.

Expected Result: Table header remains visible while other parts keep
scrolling.
Step 3: Scroll back up.

Expected Result: Table header merges back to the top of the table.

Expected Result: My investments screen is loaded.
Step 2: Select a stock item for new purchase.

Data: make total value around $1000
Expected Result: Insufficient funds error appears right away and it's
clearly worded.
Page 11
Step 1: Navigate to Home screen.

Expected Result: Home screen is loaded.
Step 2: Hit shortcut key.

Data: SHIFT+A
Expected Result: About screen is loaded.

Data: SHIFT+H
Expected Result: Home screen is loaded.

Data: SHIFT+P
Expected Result: Products page is loaded.

Data: SHIFT+N
Expected Result: New transaction screen is loaded.
Step 1: Navigate to Home screen.

Expected Result: Downloads link does not appear.
Step 2: Navigate to Products screen.

Expected Result: Downloads link appears.
Step 3: Navigate to About screen.

Expected Result: Embedded map appears in the footer.
Step 1: Navigate to New transaction screen.

Expected Result: New transaction screen is loaded.
Step 2: Focus the number type field.

Data: Transaction amount field, Price field
Expected Result: Mobile keyboard switches to numbers.
Step 3: Focus the text type fields.

Data: Stock ticker field
Expected Result: Mobile keyboard doesn't switch to numbers.
Page 12
Step 1: Open the mobile website with mobile service providers.

Data: Sprint,AT&T, T-Mobile
Expected Result: All site components load with all providers under 3
seconds.
Step 2: Open the website with Cable Service Providers.

Data: AT&T,Time Warner Cable,Verizon
Expected Result: All site components load with all providers under 2
seconds.
Step 1: Send the form when all required fields are empty.
Expected Result: Form is not accepted, warning message appears with
a list of all required fields.
Step 2: Send the form when two required fields are empty.
Data: Phone number and email address fields are empty
Expected Result: Form is not accepted, warning message appears with
a list of the two fields left empty.
Step 3: Send the form when all required fields are filled.
Expected Result: The form is accepted.
Step 1: Try the major browsers.

Data: Google Chrome 40.0.2214 and up, Mozilla Firefox 56.0 and up,
Microsoft Internet Explorer 11
Expected Result: Mobile website works with all browsers.
Step 1: Install the desktop version on Linux.

Expected Result: The application runs without errors.
Step 2: Install the desktop version on Windows.

Step 3: Install the desktop version on MacOS.

Page 13

Data: Use bandwidth throttled to 0.5 Mb/s
Expected Result: App loads only crucial components and screen loads
under 4 seconds.
Step 2: Navigate to My investments screen.

Expected Result: All necessary component load, full-screen loads
under 3 seconds.

Expected Result: App doesn't try to load, displays warning message of
too slow Internet connection.
Step 1: Test website for NIST guidelines.

Data: Resource for guidelines (see attachment)
Expected Result: Website complies with NIST security guidelines.
Step 2: Test SSL/TLS for HIPAA guidelines.

Data: Use AWS guidelines (see attachment)
Expected Result: Website complies with HIPAA security guidelines.
Step 3: Test SSL/TLS for PCI DSS security standards.

Data: See standards at https://www.pcisecuritystandards.org/
Expected Result: Website complies with PCI DSS security standards.
Step 1: Run account checks on all accounts created since the last
check.
Expected Result: No consistency problems are found.
Step 1: Access the website from mobile browser.

Expected Result: Home screen loads.
Step 2: Check if cookie values have been set.

Data: NAME=VALUE; expires=DATE; path=PATH;
domain=DOMAIN_NAME;
Expected Result: Cookie values have been set.
Page 14
Step 1: Enter a phone number that is too short.

Data: +12123
Expected Result: Value is not accepted.
Step 2: Enter a phone number that contains dashes.

Data: 901-874-6701
Step 3: Enter a phone number that contains non-numeric characters.

Data: 901-874-6701ABC
Step 4: Enter a valid phone number.

Data: 19018746701
Step 1: Open the Services menu.

Expected Result: Services for the user are limited to Standard features.
Step 2: Find the Upgrade link at the bottom of the menu bar.
Expected Result: Upgrade option is present.
Step 1: Enter a name that is too long.

Data: Adolph Blaine Charles David Earl Frederick Gerald
Step 2: Enter a name that is too short.

Data: A
Step 3: Enter a name of valid length.

Data: Joe Black
Page 15
Step 1: Initiate payment request.

Data: Account balance is sufficient
Expected Result: Transaction approved by originator bank.

Data: Account balance is insufficient
Expected Result: Transaction is rejected and user is redirected to the
merchant's website.

Data: Authentication fails
Expected Result: Transaction is rejected and user is redirected to the
merchant's website.
Step 1: Create new TPP API access request.

Data: TPP is registered in the EU PSD2 directive TPP registry
Expected Result: New TPP partner is created and API access is granted.
Step 2: Create new TPP API access request.

Data: TPP is not registered in the EU PSD2 directive TPP registry
Expected Result: API access is denied.
Step 1: Login as employee to TPP partner database.

Data: Use level 3 clearance
Expected Result: Access is granted.
Step 1: Click on instructions icon next to ZIP code field.

Expected Result: Instructions appear.
Step 2: Click on instructions icon next to Bank account field.

Step 3: Click on instructions icon next to Phone number field.

Step 4: Find instruction to Name and Age fields.

Expected Result: No instruction icons next to Name and Age fields.
Step 1: Initiate a money transfer.

Data: Amount should be other than $0. Transfer is successful
Expected Result: Push notification is received on mobile device.
Step 2: Click link in push notification.

Expected Result: Transaction details are open in app.
Page 16
Step 1: Open the Services menu.

Expected Result: Services for the user are marked with Premium logo.
Step 2: Find the Upgrade link at the bottom of the menu bar.
Expected Result: Upgrade option is not present.
Step 1: Create a selfie.

Data: Account holder in Free tier
Expected Result: Selfie is submitted and saved.
Step 2: Image file is uploaded to server.

Data: Selfie is made of the same person as account holder ID
Expected Result: File is successfully uploaded.
Step 3: Script compares previously scanned ID image with selfie.

Expected Result: Match found and identity confirmed.
Step 1: Create a selfie.

Data: Account holder in Free tier
Expected Result: Selfie is submitted and saved.
Step 2: Image file is uploaded to server.

Data: Selfie is not made of the same person as account holder ID
Expected Result: File is successfully uploaded.
Step 3: Script compares previously scanned ID image with selfie.

Expected Result: Match not found and identity not confirmed.
Step 1: Navigate to the Home screen.

Expected Result: Financial goal is present at the top of the screen.
Step 2: Navigate to Accounts overview screen.


Step 4: Navigate to any other screen.

Data: Transactions history, new transaction, bills
Expected Result: Financial goal is not present.
Page 17
Step 1: Submit a payment transaction.

Data: Simulate a timeout error
Expected Result: Transaction is not completed, email notification sent
out.
Step 2: Submit same payment transaction.

Data: Submit transaction within 1 minute of previous
Expected Result: Transaction is completed only once.
Step 1: Select the US as location.

Expected Result: App language is English.
Step 2: Select Germany as location.

Expected Result: App language is German.
Step 3: Select China as location.

Expected Result: App language is Chinese.
xcel Exporter for Jira
Page 18
Pre-Conditions association with a Test Test Sets association with a Test

[EBANK-34] Test user account balance is zero [EBANK-39] Immediate payment transactions
[EBANK-59] Banking workflows and business
requirements
[EBANK-29] Test user is logged in [EBANK-62] User Experience and Interface
[EBANK-62] User Experience and Interface
Page 19
[EBANK-37] App speed and usability
[EBANK-63] Edge cases and overload scenarios
[EBANK-34] Test user account balance is zero [EBANK-38] API Testing for Payment Service
Directive
Page 20
[EBANK-35] Mobile app is installable from [EBANK-37] App speed and usability
PlayStore
Page 21

[EBANK-62] User Experience and Interface
[EBANK-28] Transaction is already started [EBANK-36] Security and compliance
[EBANK-36] Security and compliance
Page 22

[EBANK-61] Account holders data integrity
[EBANK-27] HTML consistency check [EBANK-36] Security and compliance
Page 23
[EBANK-32] Standard tier user is logged in [EBANK-63] Edge cases and overload scenarios
Page 24
[EBANK-39] Immediate payment transactions
[EBANK-38] API Testing for Payment Service

Directive
[EBANK-38] API Testing for Payment Service

Directive
[EBANK-29] Test user is logged in [EBANK-37] App speed and usability
[EBANK-29] Test user is logged in [EBANK-58] Test [EBANK-39] Immediate payment transactions
user account balance is not zero
Page 25
[EBANK-30] Premium tier user is logged in [EBANK-63] Edge cases and overload scenarios
[EBANK-29] Test user is logged in [EBANK-59] Banking workflows and business

requirements
[EBANK-29] Test user is logged in [EBANK-59] Banking workflows and business

requirements
[EBANK-33] Financial goas has been created by [EBANK-62] User Experience and Interface
user
Page 26
Page 27
Test Plans associated with a Test Test Repository Path Links

[EBANK-60] PSD2 functional aspects /testing/2020/scenarios EBANK-54
[EBANK-66] User Experience Boost /testing/2020/smoke tests EBANK-63

[EBANK-67] Internationalization
[EBANK-66] User Experience Boost /testing/2020/smoke tests

Page 28
[EBANK-66] User Experience Boost /testing/2020/scenarios
[EBANK-60] PSD2 functional aspects /testing/2020/scenarios EBANK-54

Page 29
Page 30

[EBANK-48] Features and security testing /testing/2020/smoke tests EBANK-56

for versions after 1.1
[EBANK-48] Features and security testing /testing/2020/scenarios

Page 31


for versions after 1.1 [EBANK-66] User
Experience Boost
[EBANK-48] Features and security testing /testing/2020/smoke tests EBANK-55

Page 32

Page 33
[EBANK-60] PSD2 functional aspects /testing/2020/smoke tests
[EBANK-60] PSD2 functional aspects /testing/2020/smoke tests EBANK-52
[EBANK-60] PSD2 functional aspects /testing/2020/smoke tests EBANK-52, EBANK-53

[EBANK-66] User Experience Boost
[EBANK-48] Features and security testing /testing/2020/smoke tests

Page 34
[EBANK-60] PSD2 functional aspects /testing/2020/scenarios

[EBANK-66] User Experience Boost
Page 35
[EBANK-48] Features and security testing /testing/2020/smoke tests

Page 36
TCID Test Summary Description Component
Action Data result max number of executions
f executions

Jira Xray Tests With Test Steps

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Jira Xray Tests With Test Steps

Uploaded by

Copyright:

Available Formats

Tests with Test Steps Generated with the Better Excel Plugin for JIRATue Feb 11 09:43:59 CET

for JIRATue Feb 11 09:43:59 CET 2020

T Key Summary Test Type

Test EBANK-10 Abbreviations are consistently

Test EBANK-11 Confirmations are prompted

Test EBANK-12 Type ahead feature is default

Test EBANK-13 Table scrolling edge cases are

Test EBANK-14 Insufficient funds notifications

Test EBANK-15 All documented shortcut keys

Test EBANK-16 Irrelevant menu items don'tManual

Test EBANK-17 Keyboard switching is automatic

Test EBANK-18 Loading website with various

Test EBANK-2 Test the behavior of required

Test EBANK-20 Mobile browser compatibility

Test EBANK-22 Desktop Operating System Manual

Test EBANK-23 Response time test at different

Test EBANK-24 Verify required SSL securityManual

Test EBANK-25 Database consistency test Manual

Test EBANK-26 HTTP protocol used to storeManual

Test EBANK-3 Enter different data types Manual

Test EBANK-31 Onboarding instructions depend

Test EBANK-4 Use various text field widthsManual

Test EBANK-40 Payment verifications performed

Test EBANK-41 New third-party request canManual

Test EBANK-42 TPP list can be accessed by Manual

Test EBANK-5 Behavior of form instructions

Test EBANK-57 Transfer push notifications Manual

Test EBANK-6 Onboarding instructions depend

Test EBANK-64 Scanned account holder ID Manual

Test EBANK-65 Scanned account holder ID Manual

Test EBANK-7 Financial goal progress bar Manual

Test EBANK-8 Payment transaction submitted

Test EBANK-9 Language is automatically selected

Manual Test Steps

Step 2: Select the card type of your choice.

Step 3: Submit the payment transaction.

Step 1: Navigate to About screen.

Step 2: Hit CTRL+F to search.

Step 3: Search for an abbreviation.

Step 4: Search for an abbreviation.

Step 1: Navigate to the Registration screen.

Step 2: Fill the Name field.

Step 3: Fill the Phone number field.

Step 4: Fill the Address field.

Step 5: Navigate back to the Home screen.

Step 1: Navigate to the Support screen.

Step 2: Edit the Name field.

Step 3: Click name Christina.

Step 1: Navigate to the My investments screen.

Step 2: Scroll down to the bottom of the table.

Step 3: Scroll back up.

Step 1: Navigate to the My investments screen.

Step 2: Select a stock item for new purchase.

Step 1: Navigate to Home screen.

Step 2: Hit shortcut key.

Step 3: Hit shortcut key.

Step 4: Hit shortcut key.

Step 5: Hit shortcut key.

Step 1: Navigate to Home screen.

Step 2: Navigate to Products screen.

Step 3: Navigate to About screen.

Step 1: Navigate to New transaction screen.