Web browsers: Internet Explorer, Opera, Netscape
Web integration templates:
Design for RO, EN
Link redirection for RO, EN
Text size, colors and page look
coherence of the templates between the two languages
Problems from the demo (please refer to Summary_reserves_demo.doc sent on 26-th of April):
FM_R1 Map does not contain scales
FM_R2 Active tracking does not have the opti 111k1019b on to add user to tracking but only to replace
FM_R3 Java script problem: when trying to make zoom on the image by directly clicking with the mouse on the map, the selected zone is (red rectangle) appear in other place than the one selected with the mouse and the zooming is made on other region than selected.
FM_R4 Omni-directional antenna coverage display
FM_R5 In active tracking, I click on Add new tracking, non-recurring, within hours in the past/future then it creates the tracking as active without error; when I select the tracking and I click on Refresh location and map, then wrong image is displayed (figure 2 below) and the tracking is not displayed as active
FM_R6 If I locate an active tracking and I access big map option, then I receive the following screen (figure 3 below) having Upravit in Slovakian language.
Translations: RO, EN
Correctitude
Lack of Slovak expressions
Privacy: possibility to set tracking only within working hours
Authentication:
Login into the application
Check user types privileges: access to features and information within the application
Check the ability of the user to remain connect or to connect again after its account has been deleted
Features
Current location (MSISDN, group, alias). Check place name, all zoom levels, map look, big map, small map.
Create new tracking: check that date and hour limit are respected, periodicity is respected, add a MSISDN, add a group to the tracking, stop tracking after x cycles, stop tracking by date, no restriction. Check the indication of the position number on the tracking displayed on the map.
Check existing tracking: click on the tracking name and check the information displayed, click on modify and check the possibility of modifying the existing tracking, check the add new tracking option form this page, remove the tracking while active, remove the tracking while stopped, check pause option, refresh location and map, big/small map, zoom levels, open map in new window
Location history: specify starting/ending date and hour, for a certain MSIDN, for a certain group, check location history after accessing an active tracking (see if only the MSIDN belonging to it are displayed or not), for an alias, export data into a txt/xls file (check correctitude and format), select/deselect all, display all on the map (check this considering a lot of location -hundreds/thousands- for a certain MSISDN/for more MSISDN having a big spreading), no MSISDN/group specified, wrong MSISDN/group name specified.
Language selection: check the redirection into the same option but the other language,
Active tracking: from starting date and hour search for tracking by name, for tracking containing certain MSISDN, certain alias
Location settings: define alias for a MSISDN, check the list of phones that are not compatible, check that the alias are defined per login
Statistics: check statistics for today, current week, last week, current billing period, previous billing period, statistics total, check statistics per group, statistics per user account
Disconnect
Check the SSL certificate and its validity
Sanity checks:
1.8.1. Log in the application
1.8.2 Request location of a MSISDN.
1.8.3 Make telnet to 213.151.208.191on port 80
Other scenarios
Application name
Stopping the application while it has some requests from the users: checking what happens with the requests -are saved or lost-, checking what happens at application restart -the requests are correctly treated and answered-
Map displayed after positioning error
Locate an user who cannot be located
Erase the browser cache and check the access application and correct user positioning
Help pages tests
Scrolling the maps in all the directions
Check the screen resolution and optimum Internet speed required by the application
Check, see and store the application flow (trace from end to end on OSK side)
Sending two successively requests (quick one after the other) for the same MSISDN
Each time a new request is generated check the last map generated on https://www1.orange.sk/lbs2/
Access Fleet Management direct on its link and via www.orange.ro
Positioning error at the first location request after the log in
2.1. Check the following phone types (color and black and white) and the content adaptation for them: , check Wap 1.x and Wap 2.x phones.
Check Orange World integration (header/footer)
Check RO/EN translations
Privacy: possibility to set tracking only within working hours
Features: (please detail firstly the features available)
Locating one MSISDN, check map displayed, user position indicated, place name,
Check map scrolling, map zooming
Search history of locations for one user and their display on map. Check the case when hundreds of positioning were made.
Check tracking for one user
Check splitting on pages mechanism
Check statistics available and how they reflect the real traffic made.
Other scenarios:
Locating a user that does not exist
Displaying on map a lot of location of the same user that are very spread
Stopping (and starting) the application while it has requests in queue for processing
Wap over CSD and over GPRS
Check, see and store the application flow (trace from end to end on OSK side)
Check case of user access to the service when the MSISDN parameter is missing from the http request header
Check case when the language parameter is not sent in the http request.
Sending two successively requests (quick one after the other) for the same MSISDN
Each time a new request is generated check the last map generated on https://www1.orange.sk/lbs2/
Sanity checks:
Make telnet on 213.151.208.139 port 80
Access via Wap the address (OSK to precise): ?
Access via Web the address (OSK to precise): ?
Log into the application
Request the position of an user
Check the following phone types (color and black and white) and the content adaptation for them: , check Wap 1.x and Wap 2.x phones.
Application tests:
Check each category and subcategory of POI
Check each POI in the answer
Check pagination
Check Orange World integration
Check content adaptation
Check positioning, distance to the POI
Check map quality, street names display
Check icon, POI positioning in the center, POI indication, POI coat in the arms
Check zoom in/out levels and image focus on POI, move around the map
Check specific data layers created for POI, check default POI to be displayed
Wap over CSD and over GPRS
Check, see and store the application flow (trace from end to end on OSK side)
Check RO/EN storyboards
Check RO/EN translations
Check all the links available within wap pages (main, back, services)
Check the disclaimer, the terms and conditions page
Check correct sending of the MSISDN and language parameters in the header of http request
Check application answer time (end-to-end)
Check privacy: disclaimer presented only first time to the user
Check user confirmation storage for 3 years
Check MMS delivery if the phones support
Check help options
Check bookmark saving possibility for map link
CERF problems: often interruptions of the service while no POI returned
Other scenarios:
Case when more POI of the same type are very close one to each other: check map, icon POI indication
User accessing service from a town with no POI into the database
User access from roaming
Stop/start the application while it has requests in queue for processing
Check case of user access to the service when the MSISDN parameter is missing from the http request header
Check case when the language parameter is not sent in the http request.
Sending two successively requests (quick one after the other) to the same category of POI
Each time a new request is generated check the last map generated on https://www1.orange.sk/lbs2/
Sanity checks:
3.17.9.1. Make telnet on 213.151.208.139 port 80
3.17.9.2. Make telnet on address ? port ? ( ORO Wap GW test)
3.17.9.3. Access on Wap the address: https://localizare.orange-gsm.com:9005/lbs/orowaplbs/welcome.jsp
3.17.9.4. Access on Web the address: https://localizare.orange-gsm.com:9005/lbs/orowaplbs/welcome.jsp
3.17.9.5. Enter into the application and request a POI and check the result received
4.1. Phone test: Check the following phone types (color and black and white) and the content adaptation for them: , check Wap 1.x and Wap 2.x phones.
4.2. Other scenarios:
4.2.1. Sending SMS with identity restriction
4.2.2 Sending SMS with notification message
4.2.3. Sending SMS from an Ericsson phone that is not SMS class 0 compatible and receiving quick the application answer. Checking the SMS class 0 text
4.2.4. Stopping/starting the application while it has requests from users in queue
4.2.5 Simulating a full queue on ORO SMSC. Check the application behavior.
4.2.6 Sending two successively requests (quick one after the other) to the same category of POI
4.3. Check, see and store the application flow (trace from end to end on OSK side)
4.4. Check privacy: disclaimer presented only first time to the user
4.5 Application features:
4.5.1 Check each category and subcategory of POI
4.5.2. Check each POI in the answer
4.5.2 Check splitting the application answer in more SMS
4.5.3 Check positioning, distance to the POI
4.5.4. Check content adaptation
4.5.5 Check map link via Wap or the MMS containing the map. Check bookmark saving possibility for map link
4.5.6 Check map quality, street names display
4.5.7 Check icon, POI positioning in the center, POI indication, POI coat in the arms
4.5.8 Check zoom in/out levels and image focus on POI, move around the map
4.5.9 Check specific data layers created for POI, check default POI to be displayed
4.5.10. Check RO translation
4.5.11. Check the disclaimer and the terms and conditions
4.5.12. Check the application answer time
4.5.13. Check user confirmation storage for 3 years
Check help option
Case when more POI of the same type are very close one to each other: check map, icon POI indication
User accessing service from a town with no POI into the database
User access from roaming
Each time a new request is generated check the last map generated on https://www1.orange.sk/lbs2/
Sanity checks:
4.5.19.1. Make telnet on the address ? port ? (SMSC)
4.5.19.2. Make telnet on the address ? port ? (to be filled in by OSK, for Find Nearest application)
4.5.19.3. Request a POI category and check the result received.
5.1. Check number of objects per layer in the database (for color and black and white maps)
5.2. Visual inspection of different layers (for color and black and white maps)
5.3. Check that the maps are in WGS_1984_UTM_Zone_35N
5.4. Check maps with map viewer
5.5. Import a map via map API: file with 0 size, file with very large size, zipped file, unzipped file.
5.6 Simulate no space on the map directory.
5.7 Check authentication
5.8. Import file with other structure than map info one
5.9 Make two successive imports one after the other and check if both are successful (one does not reset the modification the other brings)
5.10. Check the automatic correct processing of the files and its result
5.11. Check the logs of shape file conversion
5.12. Simulate the case when the production server is not available.
5.13. Switching the traffic on the back-up machine while the import was started but not ended.
5.14 GIS and LBS application restart while a map file has been imported and its processing started but not ended
5.15. Sanity check:
5.15.1. Log into the API and upload a test file and check the message displayed.
5.15.2. Make telnet on 213.151.208.191, port 80
6.1. Check authentication
Import a file via cell plan API: file with 0 size, file with very large size, zipped file, unzipped file.
6.3. Simulate no space on the directory
6.4. Make two successive imports one after the other and check that both are successful
6.5. Import a file with other structure than for the cell plan
6.6. The same tests in order to import the best server
6.7 Check the automatic correct processing of the files and its result
6.8 Simulate the case when the production server is not available.
6.9. Switching the traffic on the back-up machine while the import was started but not ended.
6.10. GMLC and LBS application restart while a map file has been imported and its processing started but not ended
6.11. Display the footprint of all the cells on the map conform to the imported data
6.12. Check in the cell plan file for the new parameter ORO requested
6.13. Sanity check:
6.13.1. Log into the API, upload a test file and see the message received
6.13.2. Make telnet on 213.151.208.191, port 80
7.1. Check authentication
Import a file via place name API: file with 0 size, file with very large size, zipped file, unzipped file.
7.3. Simulate no space on the directory
7.4. Make two successive imports one after the other and check that both are successful
7.5. Import a file with other structure than for the place name
7.6 Check the automatic correct processing of the files and its result
7.7 Simulate the case when the production server is not available.
7.8 Switching the traffic on the back-up machine while the import was started but not ended.
7.9. GIS and LBS application restart while a map file has been imported and its processing started but not ended
7.10. Display the footprint of all place name over the footprint of the cells on the map conform to the imported data
7.11. Sanity checks:
7.11.1. Log into the API, upload a test file and see the message received
7.11.2. Make telnet on 213.151.208.191, port 80
8.1. Check authentication
Import a add POI and a
8.3. Simulate no space on the directory
8.4. Make two successive (one add POI and one
8.5. Import a file with other structure than for the add/
8.6 Check the automatic correct processing of the files and its result
8.7 Simulate the case when the production server is not available.
8.8 Switching the traffic on the back-up machine while the import was started but not ended.
8.9. GIS and LBS application restart while a map file has been imported and its processing started but not ended
Possibility to see and check the details and position on the map of each uploaded POI with the map viewer
8.11. POI category list update test (update some POI categories, check the update result in the Find Nearest application)
8.12.Sanity checks:
8.12.1. Log into the API, upload a test file and see the message received
8.12.2. Make telnet on 213.151.208.191, port 80
8.12.3. Request the category of this POI and check that is was imported.
9.1. Check the correctitude of billing at content delivery and successful location
9.2. Check the credit reservation for a prepay
9.3. Check the access to LBS service from a prepay whose account is empty, inactive, valid
9.4. Check CDR format (fields correspondence within the Radius request)
9.5. Check the CDR export (Radius logs export)
9.6. Application stop/start while it has requests in queue for processing
9.7 Check a failed Radius request
9.8. Check logs of reservation requests
9.9. Check the correctitude of CDR generation for a request from each LBS application or received via GDEP.
9.10. Sanity check:
9.10.1. FTP/telnet on ?
10.1. Fleet Management:
10.1.1. Stop/start the Fleet Management Web/Wap while provisioning actors (check the correctitude of data provisioned)
10.1.2 Stop/start the Fleet Management Web/Wap while provisioning users (check the correctitude of data provisioned)
10.1.3. Stop/start the Fleet Management Web/Wap while changing user password (check the correctitude of the process)
10.1.4 Check the logs of the provisioning actors/users: add, delete, modify
10.1.5. One Fleet Management user is connected to the service; remove its account and check that he has no longer access to the service.
10.2. Find Nearest:
10.2.1. Check the auto-provisioning of the LBS users.
10.2.3 Stop/start SMS/Wap application while a user is accessing the application for the first time
10.3. Sanity checks
11.1. Fleet Management application logs: Check format, correctitude and information within the logs:
Incoming positioning request - 10000
Incoming map request - 10001
Incoming multiple positioning request - 10002
Correct positioning answer - 10100
Correct map answer - 10101
Correct multiple positioning answer - 10102
Positioning error - 10200
Map picture obtaining error - 10201
Multiple positioning error - 10202
Connection error - 10210
11.2. Find Nearest application logs: check format, correctitude and information within the logs
11.3. Location broker logs: check format, correctitude and information within the logs.
The following information from the logs should be made available in real-time:
11.4. SMS Gateway logs: check format, correctitude and information within the logs. The following information from the logs should be made available in real-time:
11.5 MMS Gateway logs: check format, correctitude and information within the logs. The following information from the logs should be made available in real-time:
Real time transaction logs: GMLC, GIS, MW, check existence and information within.
Fleet Management statistics
12.1.1. Application statistics, check if they correspond to the traffic generated
12.1.2. Statistics requested, check the availability of the statistics requested: customer subscribed to the service, number of customers, number of subscribers for each customer, info on customer Business Type, their address (city name) and on the subscription plans they have chosen, invoiced revenue (monthly fee + extra bundle revenue), discounts if any, active users: number of active users, type of bundle and usage (no of positioning) IN and OUSIDE the bundle, no of successful / unsuccessful positioning, positioning via Wap and WEB, traffic per hours within day
Find nearest statistics
12.2.1 Application statistics, check if they correspond to the traffic generated
Statistics requested, check the availability of the statistics requested: active users,
number of active users and their Customer Type (PPY, bus type), number and split of originating requests: SMS/WAP, how were the localization requests distributed among the available cities, type of POI requested: categories, subcategories, number and split of LBS Positioning: SMS/WAP, successful/unsuccessful/ no POI found, invoiced revenue, traffic per hours within day
API statistics: specific statistics for each API (please describe): number of correct / not correct files uploaded, number of successful objects imported automatically from the first time, date and time of the uploading
CTT statistics: number of opened, solved, not solved CTT, date and time of opening, solving time for each CTT, CTT grouped on problems type, statistics per duration.
GDEP statistics: number of GDEP accesses, number of simultaneous sessions, total number of successful/unsuccessful locations / maps / privacy retrieved via GDEP per period (by specifying starting/ending time), number of successful/unsuccessful locations / maps / privacy retrieved via GDEP per period (by specifying starting/ending time) grouped per GDEP account
sending small, large MMS
check MMS parameterization
check SMS parameterization for each LBS service
check WAP parameterization for each LBS service
Sanity checks:
13.5.1. SMSC: telnet on 213.151.208.151
13.5.2. MMSC: telnet on ?
13.5.3. WAP: telnet on 213.151.208.139, port 80
Simulate a correct and an incorrect location request and answer via GDEP
Simulate a correct and incorrect map request and answer via GDEP
Simulate a correct and incorrect privacy rights set request and answer via GDEP
Simulate a correct and incorrect privacy rights interrogation request and answer via GDEP.
Checking the GDEP users rights for access
Stop and start the GDEP interface while it has location, maps, privacy request in processing / answering queue.
Simulating full queue for location, map, privacy from the external clients to the system
Simulating full queue for location, map, privacy from the system to external clients
Positioning error for location requested via GDEP
Map retrieving error for map requested via GDEP
Check answer times in case of sending/receiving location, maps, privacy requests via GDEP
Check the GDEP request ORO requested and its answer. Check answer time. Check parameters.
Sanity checks:
14.13.1. Telnet on 213.151.208.191, port 80
14.13.2. Send a test request (to be proposed by OSK, for location, map, privacy) and checking the answer.
16.1. Make backup for each application and module (GMLC, GIS, MW). Check the logs of operations made.
16.2. Make a restore for each application and module (GMLC, GIS, MW). Choose the restore session desired. Check what happens with the traffic occurred while making the restore.
16.3 Make an un-restore for each application and module (GMLC, GIS, MW). Choose the un-restore session desired. Check what happens with the traffic occurred while making the un-restore.
17.1. For each LBS application and module (Fleet Management, Find Nearest, GMLC, GIS, MW) simulate the commercial launch of service by running the exact migration procedure. Check the log results of procedure executing.
For each LBS application and module (Fleet Management, Find Nearest, GMLC, GIS, MW) simulate the migration to the disaster site (back-up module) by running the exact migration procedure. Check the log results of procedure executing. Check what happens with the traffic from LBS applications, GDEP (location, maps, privacy) during this time.
For each LBS application and module (Fleet Management, Find Nearest, GMLC, GIS, MW) simulate the migration back from the disaster site (back-up module) to the main site by running the exact migration procedure. Check the log results of procedure executing. Check what happens with the traffic from LBS applications, GDEP (location, maps, privacy) during this time.
19.1 Check the availability of phone information file, the information presented and the phone types.
Check the availability of the requested KPI (KPI.doc)
Check the availability of the KPI for each API (to be completed by OSK): number of successful/unsuccessful GDEP requests per period of time -hours within day and days within month-, number of files correctly uploaded via each API per period of time, number of files incorrectly uploaded via each API grouped by cause per period of time, number of successful objects imported from the first time per period of time.
21.1. Check existence of the history with subscriber locations
21.2. Check the size and format of this information
21.3. Check the storage of the user confirmations regarding the disclaimer
Sending SOAP request with certain parameters (user location configurable, POI category, POI number to return: from 0 to a large number)
Checking the SOAP answer for the request made.
Sending an incorrect SOAP request and checking the answer.
Check the flow of sending the SOAP request and answer
Check the separator among the fields, the number of fields within the request and the answer
Sending SOAP request with a location that does
not exist in
Sending SOAP request with incorrect format of the user location
Check SOAP time (request/answer)
Sanity check (OSK to propose):
23.1. Crosscheck LBS application logs, GMLC logs, GIS logs, MW logs, history, CDRs exported and credit reservation logs: count the requests, check correspondence between date and hour, requester/requested MSISDN/application, information requested
24.1. Check the possibility of open a CTT
24.2. Check the possibility of close a CTT
24.3. Check the open/closed CTT by date, by time, by problem category.
24.4. Check the CTT solving status.
24.5. Sanity check:
24.5.1. Telnet on ? port? (OSK to fill in)
24.5.2. Log in into the application.
25.1. Check the possibility of taking the files/logs for ORO DWHS, check the size of the information and the structure.
25.2. Sanity checks: ftp to ? (OSK to fill in)
26.1. Make a switch to the back-up lines. Check what happens with the applications traffic.
26.2. Make the switch back to the existing VPN. Check what happens with the applications traffic.
26.3 Data links configuration on both ends
26.4. Sanity checks:
Elicom VPN:
ping from 213.151.205.11 to 62.217.245.65
ping from 62.217.245.65 to
telnet from 213.151.208.149 to 80.96.28.35, port 80
telnet from 213.151.208.150 to
80.96.28.35, port 80
telnet from 213.151.208.187 to 80.96.28.35, port 80
telnet from 213.151.208.151 to 80.96.28.35, port 80
telnet from to 213.151.208.191, port 80 (map generation interface)
IT VPN:
ping from 62.217.251.227 to
A=IP address from
telnet from A to 213.151.208.154, port 80 (cell plan/maps/place name/street table update API test, users location archive test, history tool -logs- test, CTT test, web applications access test)
telnet from A to 213.151.208.154, port 9005 (test web application)
telnet from A to 213.151.208.139, port 81 (phone API test and commercial)
telnet from A to 213.151.208.191, port 80 (cell plan/maps/place name/street table API commercial, POI category list update, users location archive commercial, history tool -logs- commercial, CTT commercial, web applications access commercial)
B=IP address from 62.217.251.160/27
telnet from B to 213.151.208.154, port 80 (daily logs test, users location archive test, history tool -logs- test, CDR download test, web applications access test, location/privacy API test)
telnet from A to 213.151.208.191, port 80 (map generation interface, daily logs commercial, users location archive commercial, history tool -logs- commercial, CDR download commercial, web applications access commercial, location/privacy API commercial)
TD VPN:
ping from 62.217.245.200 to 213.151.205.11
C=IP address from
telnet from to C (test SMSC connections)
telnet from C to 213.151.208.158, port 80 (WAP test)
telnet from C to 213.151.208.139, port 80 (WAP commercial)
telnet from to C (commercial SMSC connections)
Leased line (to be filled in afterwards):
GMLC
Simulating a full queue form the applications and a new request coming
Receiving an incorrect location request from an application
Receiving an empty request from the application
Requests received while migrating from a GMPC to another
Simultaneous number of transactions greater than the license granted, check the behavior
GIS
Simulating a full queue from the applications and a new request coming
Receiving an incorrect GIS request from an application
Receiving an empty GIS request from the application
Requests received while migrating from a GIS to another
Simultaneous number of transactions greater than the license granted, check the behavior
MW
Middleware stop and start while GDEP requests are in queue for processing
Middleware switching while GDEP requests are in queue for processing
Middleware authentication and authorization check for external clients (IP addresses, user name, password).
Other tests
ATI test with phone switched off
ATI test with out of coverage phone
ATI test with a phone from roaming
Simulating a full queue and a new request coming
Checking with network analyzer that the user location retrieved from GMPC is correct
Locating a MSISDN that has no SMS provisioned into the HLR (Location Age smaller and greater than 5 minutes)
MO-LR, Location Age smaller and greater than 5 minutes
MT-LR, Location Age smaller and greater than 5 minutes
Check the possibility of locating a MSISDN that has not voice/SMS/data services activated in the network
Check the possibility of locating MSISDN that have barring at HLR level (CBOI, CBO)
Check the possibility of locating MSISDN with specific marks in the HLR (Camel incoming/outgoing, OS2 -MVPN-, OS4 -closed, USSD marks for PPY, SMS marks for PPY)
Check the possibility of locating a PPY/MVPN/PPD during WAP over CSD/WAP over GPRS/USSD, GPRS, idle state, during voice call, while located on a repeater
29.1 Check the behavior of location an MSIDN that is during a voice call/or not and is doing handover
29.2 Check the correctitude of location while the subscriber is on move with the care with certain speed
29.3 Check the correctitude of tracking when subscriber is in town/rural area
29.4 Check the correctitude of location when the user is in the mountains (under reflection influence)
Check the effect of random propagation
To find out the algorithms of cell selection in the mobiles and radio thresholds that impose the mobiles to stay on a certain cell.
|
