Tuesday, December 30, 2014
Tuesday, November 18, 2014
TC for mobile
No.
Module
>>> Sub-Module
>>>Test Case Description
>>>Expected Result
1
Installation
Verify that application can be Installed Successfully.
Application should be able to install successfully.
2
Uninstallation
Verify that application can be uninstalled successfully.
User should be able to uninstall the application successfully.
3
Network Test Cases
Verify the behavior of application when there is Network problem and user is performing operations for data call.
User should get proper error message like “Network error. Please try after some time”
4
Verify that user is able to establish data call when Network is back in action.
User should be able to establish data call when Network is back in action.
5
Voice Call Handling
Call Accept
Verify that user can accept Voice call at the time when application is running and can resume back in application from the same point.
User should be able to accept Voice call at the time when application is running and can resume back in application from the same point.
6
Call Rejection
Verify that user can reject the Voice call at the time when application is running and can resume back in application from the same point.
User should be able to reject the Voice call at the time when application is running and can resume back in application from the same point.
7
Call Establish
Verify that user can establish a Voice call in case when application data call is running in background.
User should be able to establish a Voice call in case when application data call is running in background.
8
SMS Handling
Verify that user can get SMS alert when application is running.
User should be able to get SMS alert when application is running.
9
Verify that user can resume back from the same point after reading the SMS.
User should be able to resume back from the same point after reading the SMS.
10
Unmapped keys
Verify that unmapped keys are not working on any screen of application.
Unmapped keys should not work on any screen of application.
11
Application Logo
Verify that application logo with Application Name is present in application manager and user can select it.
Application logo with Application name should be present in application manager and user can select it.
12
Splash
Verify that when user selects application logo in application manager splash is displayed.
When user selects application logo in application manager splash should be displayed.
13
Note that Splash do not remain for fore than 3 seconds.
Splash should not remain for fore than 3 seconds.
14
Low Memory
Verify that application displays proper error message when device memory is low and exits gracefully from the situation.
Application should display proper error message when device memory is low and exits gracefully from the situation.
15
Clear Key
Verify that clear key should navigate the user to previous screen.
Clear key should navigate the user to previous screen.
16
End Key
Verify that End Key should navigate the user to native OEM screen.
End Key should navigate the user to native OEM screen.
17
Visual Feedback
Verify that there is visual feedback when response to any action takes more than 3 seconds.
There should be visual feedback given when response time for any action is more than 3 second.
18
Continual Keypad Entry
Verify that continual key pad entry do not cause any problem.
Continual key pad entry should not cause any problem in application.
19
Exit Application
Verify that user is able to exit from application with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
User should be able to exit with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
20
Charger Effect
Verify that when application is running then inserting and removing charger do not cause any problem and proper message is displayed when charger is inserted in device.
When application is running then inserting and removing charger should not cause any problem and proper message should be displayed when charger is inserted in device.
21
Low Battery
Verify that when application is running and battery is low then proper message is displayed to the user.
When application is running and battery is low then proper message is displayed to the user telling user that battery is low.
22
Removal of Battery
Verify that removal of battery at the time of application data call is going on do not cause interruption and data call is completed after battery is inserted back in the device.
Removal of battery at the time of application data call is going on should not cause interruption and data call should be completed after battery is inserted back in the device.
23
Battery Consumption
Verify that application does not consume battery excessively.
The application should not consume battery excessively.
24
Application Start/ Restart
1. Find the application icon and select it 2. “Press a button” on the device to launch the app. 3.Observe the application launch In the timeline defined
Application must not take more than 25s to start.
25
Application Side Effects
Make sure that your application is not causing other applications of device to hamper.
Installed application should not cause other applications of device to hamper.
26
External incoming communication – infrared
Application should gracefully handle the condition when incoming communication is made via Infra Red [Send a file using Infrared (if applicable) to the device application presents the user]
When the incoming communication enters the device the application must at least respect one of the following: a) Go into pause state, after the user exits the communication, the application presents the user with a continue option or is continued automatically from the point it was suspended at b) Give a visual or audible notification The application must not crash or hung.
Module
>>> Sub-Module
>>>Test Case Description
>>>Expected Result
1
Installation
Verify that application can be Installed Successfully.
Application should be able to install successfully.
2
Uninstallation
Verify that application can be uninstalled successfully.
User should be able to uninstall the application successfully.
3
Network Test Cases
Verify the behavior of application when there is Network problem and user is performing operations for data call.
User should get proper error message like “Network error. Please try after some time”
4
Verify that user is able to establish data call when Network is back in action.
User should be able to establish data call when Network is back in action.
5
Voice Call Handling
Call Accept
Verify that user can accept Voice call at the time when application is running and can resume back in application from the same point.
User should be able to accept Voice call at the time when application is running and can resume back in application from the same point.
6
Call Rejection
Verify that user can reject the Voice call at the time when application is running and can resume back in application from the same point.
User should be able to reject the Voice call at the time when application is running and can resume back in application from the same point.
7
Call Establish
Verify that user can establish a Voice call in case when application data call is running in background.
User should be able to establish a Voice call in case when application data call is running in background.
8
SMS Handling
Verify that user can get SMS alert when application is running.
User should be able to get SMS alert when application is running.
9
Verify that user can resume back from the same point after reading the SMS.
User should be able to resume back from the same point after reading the SMS.
10
Unmapped keys
Verify that unmapped keys are not working on any screen of application.
Unmapped keys should not work on any screen of application.
11
Application Logo
Verify that application logo with Application Name is present in application manager and user can select it.
Application logo with Application name should be present in application manager and user can select it.
12
Splash
Verify that when user selects application logo in application manager splash is displayed.
When user selects application logo in application manager splash should be displayed.
13
Note that Splash do not remain for fore than 3 seconds.
Splash should not remain for fore than 3 seconds.
14
Low Memory
Verify that application displays proper error message when device memory is low and exits gracefully from the situation.
Application should display proper error message when device memory is low and exits gracefully from the situation.
15
Clear Key
Verify that clear key should navigate the user to previous screen.
Clear key should navigate the user to previous screen.
16
End Key
Verify that End Key should navigate the user to native OEM screen.
End Key should navigate the user to native OEM screen.
17
Visual Feedback
Verify that there is visual feedback when response to any action takes more than 3 seconds.
There should be visual feedback given when response time for any action is more than 3 second.
18
Continual Keypad Entry
Verify that continual key pad entry do not cause any problem.
Continual key pad entry should not cause any problem in application.
19
Exit Application
Verify that user is able to exit from application with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
User should be able to exit with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
20
Charger Effect
Verify that when application is running then inserting and removing charger do not cause any problem and proper message is displayed when charger is inserted in device.
When application is running then inserting and removing charger should not cause any problem and proper message should be displayed when charger is inserted in device.
21
Low Battery
Verify that when application is running and battery is low then proper message is displayed to the user.
When application is running and battery is low then proper message is displayed to the user telling user that battery is low.
22
Removal of Battery
Verify that removal of battery at the time of application data call is going on do not cause interruption and data call is completed after battery is inserted back in the device.
Removal of battery at the time of application data call is going on should not cause interruption and data call should be completed after battery is inserted back in the device.
23
Battery Consumption
Verify that application does not consume battery excessively.
The application should not consume battery excessively.
24
Application Start/ Restart
1. Find the application icon and select it 2. “Press a button” on the device to launch the app. 3.Observe the application launch In the timeline defined
Application must not take more than 25s to start.
25
Application Side Effects
Make sure that your application is not causing other applications of device to hamper.
Installed application should not cause other applications of device to hamper.
26
External incoming communication – infrared
Application should gracefully handle the condition when incoming communication is made via Infra Red [Send a file using Infrared (if applicable) to the device application presents the user]
When the incoming communication enters the device the application must at least respect one of the following: a) Go into pause state, after the user exits the communication, the application presents the user with a continue option or is continued automatically from the point it was suspended at b) Give a visual or audible notification The application must not crash or hung.
[note for me] TC for ATM
1) Insertion of ATM card with success.
2) Incorrect ATM Card Insertion – Leading to unsuccessful operation.
3) ATM Card of an invalid account – Leading to unsuccessful operation.
4) Successful feeding of ATM PIN Number.
5) Incorrect ATM PIN Number feeding 3 times - Leading to unsuccessful operation.
6) Selection of language of operation, with success.
7) Selection of Type of Bank Account with success.
8) Incorrect Bank Account type Selection in respect to the type of ATM Card inserted - Leading to unsuccessful operation.
9) Selection of withdrawal option with success.
10) Selection of Amount to be withdrawn with success.
11) Incorrect Currency denominations - Leading to unsuccessful operation.
12) Successful completion of withdrawal of money.
13) Amount to be withdrawn in excess of the available Balance - Leading to unsuccessful operation.
14) Shortage of Currency Notes in ATM - Leading to unsuccessful operation.
15) Amount to be withdrawn in excess of the daily withdrawal limit - Leading to unsuccessful operation.
16) ATM link to the Bank Server not available at the moment - Leading to unsuccessful operation.
17) Clicking of the Cancel button after inserting the ATM card - Leading to unsuccessful operation.
18) Clicking of the Cancel button after feeding the ATM PIN Number - Leading to unsuccessful operation.
19) Clicking of the Cancel button after selection of language of operation - Leading to unsuccessful operation.
20) Clicking of the Cancel button after selection of Type of Bank Account - Leading to unsuccessful operation.
21) Clicking of the Cancel button after selection of Amount of withdrawal - Leading to unsuccessful operation.
22) Clicking of the Cancel button after feeding the amount to be withdrawn - Leading to unsuccessful operation.
2) Incorrect ATM Card Insertion – Leading to unsuccessful operation.
3) ATM Card of an invalid account – Leading to unsuccessful operation.
4) Successful feeding of ATM PIN Number.
5) Incorrect ATM PIN Number feeding 3 times - Leading to unsuccessful operation.
6) Selection of language of operation, with success.
7) Selection of Type of Bank Account with success.
8) Incorrect Bank Account type Selection in respect to the type of ATM Card inserted - Leading to unsuccessful operation.
9) Selection of withdrawal option with success.
10) Selection of Amount to be withdrawn with success.
11) Incorrect Currency denominations - Leading to unsuccessful operation.
12) Successful completion of withdrawal of money.
13) Amount to be withdrawn in excess of the available Balance - Leading to unsuccessful operation.
14) Shortage of Currency Notes in ATM - Leading to unsuccessful operation.
15) Amount to be withdrawn in excess of the daily withdrawal limit - Leading to unsuccessful operation.
16) ATM link to the Bank Server not available at the moment - Leading to unsuccessful operation.
17) Clicking of the Cancel button after inserting the ATM card - Leading to unsuccessful operation.
18) Clicking of the Cancel button after feeding the ATM PIN Number - Leading to unsuccessful operation.
19) Clicking of the Cancel button after selection of language of operation - Leading to unsuccessful operation.
20) Clicking of the Cancel button after selection of Type of Bank Account - Leading to unsuccessful operation.
21) Clicking of the Cancel button after selection of Amount of withdrawal - Leading to unsuccessful operation.
22) Clicking of the Cancel button after feeding the amount to be withdrawn - Leading to unsuccessful operation.
Thursday, November 13, 2014
Tuesday, November 11, 2014
[annotation] Make a Test Plan by JMeter tool
Make a Test Plan by Jmeter tool
[11/11/2014]
Before testing a project, we’re
make a Test Plan which is support Jmeter. We have to note Thread groups,
Listener, Assertions, Sample generating controllers, logic controllers, etc
Remember: one Test Plan have a
thread group at least
Explain keyword below
1.
Samplers: Elements that send request to servers; there are some
request: HTTP/ HTTPS, FTP, SOAP, JDBC, “java”
2.
Listeners: there’re collected results of your’s Run test
3.
Timers : Being use to which insert (độ trễ) giữa những request “to
have make your’s test “hiện thực hơn” more real *.*
4.
Logic Controllers: Nếu: những request được định nghĩa trong Test
Plan của bạn sẽ thực thi phụ thuộc vào 1
vài logic thì bạn cần đền Logic controllers ( if requests are define in your’s
Test Plan that will execute and depend on some logic then you need Logic
Controllers. We’re appropriate with if-then-else structure and loop in java or
whatever (bất cứ) programming language other.
5.
Configuration Elements: that work with Samplers anyway (bằng
cách) insert/ update information general with requests
6.
Assertions: permiting you test ( nếu phản ứng/ responses bạn lấy
chứa dữ liệu mong đợi hay nhận trong phạm vi/ area thời gian đã định)
Tutorial set up
and testing
Step 01: Running
Jmeter file
Step 02: Create a
Thread group by right-click mouse Test Plan element => selected “ADD” choose
Thread group option ( next step, we’re assume number of count users and users
quantity are repeat – giả lập SL user và SL lặp cho test plan)
Viewing the
screen was create below:
Maybe a number of
attributes setting/ establish below:
1.
Name: we can create any of name for Thread group
2.
Number of Threads: we can input more threads to
have assume. Each users independent ( được đại diện bởi mỗi Thread). So we
wanna assume with five users then we have to input data for it
3.
Ramp-Up Period: (cho biết time đưa ra bởi Jmeter
để tạo tất cả những Thread cần thiết. Ex: If we establishs about ten minutes
for five Threads then Jmeter will be perform in ten minutes to which creates
five Threads. Moreover,
Monday, November 10, 2014
[annotation about security]
- About public key and private key [newsfeed]
1. Using public key which to comfirm about a signature
2. Using private key that to create a signature ( ký 1 thông điệp)
-----------------------------------------
1. Tổ hợp khóa dùng chung chỉ có 2 người biết
1. Using public key which to comfirm about a signature
2. Using private key that to create a signature ( ký 1 thông điệp)
1. Tổ hợp khóa dùng chung chỉ có 2 người biết
Sunday, November 9, 2014
Subscribe to:
Posts (Atom)