Testing

From EPOD

Database

The development and test database is hosted on the calidus_demo server (IP: 10.43.0.73, DNS: calidus_demo, URL: www.calidus-web.com).

The database is Microsoft SQLServer 2008.

PDA Server

The PDA server is hosted on calidus_demo through Microsoft IIS. The url is www.calidus-demo.com:9091/Calidus_EPOD/Calidus_EPOD.asmx.

Admin

The Admin system is hosted on calidus_demo through Microsoft IIS. The url is www.calidus-demo.com:9091

The system can be run through any modern browser.

A full test plan exists to run through all screens and functionality.

Windows Mobile PDA Client

This requires the Microsoft Windows Mobile 6.5 Developer Tool Kit, available from http://www.microsoft.com/download/en/details.aspx?id=17284

Download the US version: Windows Mobile 6.5 Professional Developer Tool Kit (USA).msi

  • Install the toolkit.
  • Choose Windows Mobile 6 SDK/Standalone Emulator Images/US English/WM 6.5 Professional

This will start the emulator.

  • When started, change the regional settings to UK and the timezone to GMT.
  • Start Microsoft ActiveSync.
  • Choose File/Connection Settings from the menu.
  • Check Allow connections to one of the following:.
  • Choose DMA.
  • Click OK
  • Choose Windows Mobile 6 SDK/Tools/Device Emulator Manager. Your emulator should be shown on a browser.
  • Right-click and choose Cradle.
  • This will connect to ActiveSync.
  • Click Cancel.
  • Click Explore.
  • Put the PDA application installers onto the device in the Programs folder.
  • On the emulator, open the File Explorer from the Start menu.
  • Browse to the program directory and click on each installer in turn, installing them. For more details on the PDA installation process, see the page 'Device Installation'.
  • Click File/Save State and Exit - this will save the emulator with the software installed.

The emulator is now ready for use.

A full test plan exists to run through all screens and functionality.

Android Client

Preparation and Installation

You need to download and install the Android SDK - latest here: http://dl.google.com/android/installer_r21.1-windows.exe. You should check the page at http://developer.android.com/sdk/index.html for the latest.

When installed, run SDK Manager, to download the different target platforms. Install the following as minimum:

  • Tools
    • Android SDK Tools
    • Android SDK Platform-tools
  • Android 2.3.3 (API 10)
    • SDK Platform
    • Google APIs
  • Extras
    • Google USB Driver

Note Note: You can optionally add in more modern Android versions if desired - the system works on everything up to and including API 16 (Android 4.1), but these take more memory and processing, so will run slower in the emulator, and will also affect the defaults when setting up a new emulator.

Set-up

Set up an emulator through AVD Manager, as below, using the New button:

  • Name: Demo
  • CPU/ABI: (ARM (armeabi)
  • Target: Android 2.3.3 (API level 10)
  • Skin: WVGA854
  • SD Card: 512M
  • Snapshot: true
  • hw.lcd.density: 240
  • hw.gps: yes
  • hw.keyboard: yes
  • vm.heapSize: 24
  • snapshot.present: true
  • hw.ramSize: 256

All the properties above the line are required when you choose to create a new emulator, those below the line are optional and are added using the Hardware Properties section in the New dialogue.

Note Note: The Ram could be made a little larger, (for example 512 Mb), but this configuration runs the system well.

Installing the App

  • Run the emulator.
  • Set the time (using the Menu button/Settings/Date and Time)
  • When started, install the apk through adb command line from the directory with the apk with:
    • C:\Users\yourusername\AppData\Local\Android\android-sdk\platform-tools\adb.exe install "CALIDUS ePOD.apk"
  • Note that this installation can take some time to complete.

Configuring the App

  • On start-up of the application, you will be requested to do some set-up. Choose Yes.
  • Enter the Site you have been provided.
  • Language does not currently change anything, although it will, and Chinese (as listed) is an option.
  • Style is your choice, Default is OBS standard, red is very different on the job list.
  • Enter the Webservice - usually one of:
    • http://www.calidus-web.com:9093/epod_dev
    • http://www.calidus-web.com:9093/epod_test
    • http://www.calidus-web.com:9091/epod_uat
    • http://www.calidus-web.com:9091/epod_trial
    • http://www.calidus-web.com:9091/epod_demo
  • It is advised to change Update Interval to 30 seconds.
  • Exit with the Back button on the emulator, or ESC.
  • Clear the popup with the Back button on the emulator, or ESC.

Using the Emulator

  • Selecting items can be done using the left mouse click.
  • Scrolling windows can be scrolled using dragging - left-click-hold on the window, move the mouse and then release the left mouse button.
  • Swiping on Tabbed windows can be achieved by dragging left or right on the window.
  • Text entry can be made through the pop-up keyboard on the device window or the emulator keypad.
  • With the emulator configured as above, the PC keyboard can also be used to enter data in text boxes. The numeric keypad will not work in Numlock mode.
  • ESC can be used as the Back key, to clear popup dialogues, move back one screen, clear drop-down lists, etc.
  • The Back, Menu, Search and Home buttons can be found on the soft keyboard in the emulator window.
  • You can change orientation using the numeric keypad (while NOT in numlock mode), using 7 and 9 to rotate the device).
  • You can navigate through options on the device with the cursor keys or the mouse wheel, if configured.
  • Notes:
    • The Tab key does NOT move the entry to the next text box - this is a Windows convention.
    • You can't copy from Windows and paste into the emulator.

Application Use

Documentation

Note Note: This section is not intended as a replacement for standard procedures, but instead a reminder of the responsibilities for developers and testers.

  • When development is complete, developers should unit test their code. Although this step is required, it is not necessarily required to produce a proof of testing document, unless this code is not being system tested before release.
  • A Proof of testing document should be produced. This should be named with the Log Number and an indication of its function (i.e. POT_123456_DEV), can be produced in any document format (e.g. txt, rtf, doc, pdf, xls, etc) and should be stored in an EPOD subfolder of the Test_Logs area of the SpekeFS server (\\10.43.0.21\Test_Logs\EPOD) - a subfolder should be created here named as the log number (henceforth known as the Testing Folder) and all related documents stored in here. The document should provide evidence of testing and proof of pass.
  • If there is a test plan associated to this development, this or the enclosing Functional Specification should be stored in the Log's Testing Folder. If one has been created for the unit testing, this should also be stored here. Again, the document should be named reasonably (i.e. TP_123456_DEV).
  • When unit testing is complete, the log should be assigned to the development manager or testing manager, for allocation to a tester - this is done through Supimix. The status and sub-status should also be changed. When prompted, the comment should reference the POT document(s) created i.e. "Unit testing passed - POT here: \\10.43.0.21\Test_Logs\EPOD\123456\POT_123456_DEV.txt". Note Note: It is acceptable to use the drive letter "L" to map to \\10.43.0.21\Test_Logs\ if preferred, resulting in "L:\EPOD\...".
  • When allocated to a tester, the status and sub-status should be changed to reflect "in test".
  • A Proof of testing document should be produced. This should reference the tests of any test plan available. The document should provide evidence of testing and proof of pass. The document should be stored in the Log's Testing Folder and named similarly to the unit test proof i.e. POT_123456.doc. Note Note: Proof of testing documents are required at this stage.
  • Should any failures occur, these should be fed back to the development manager, by updating the log's status and sub-status and commenting with a pointer to the POT document. If this is the case, any subsequent POT documents produced should clearly indicate the cycle of testing i.e. POT_123456_2.doc.
  • Once testing is complete and passed, the log should be assigned to the development manager or testing manager, for releasing - this is done through Supimix. The status and sub-status should also be changed. When prompted, the comment should reference the POT document(s) created i.e. "System testing passed - POT here: \\10.43.0.21\Test_Logs\EPOD\123456\POT_123456.doc".

See the release process for further information.

Retrieved from "https://calidusassist.adcservices.apteancloud.com/calidus-assist/EPOD/index.php?title=Testing&oldid=747"