Testing - Revision history

Anw: /* Documentation */

2013-09-18T10:14:21Z

Documentation

← Older revision		Revision as of 12:14, 18 September 2013
Line 124:		Line 124:

	* 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.		* 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 ~~it's~~ 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.		* 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).		* 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}} 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 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}} It is acceptable to use the drive letter "L" to map to \\10.43.0.21\Test_Logs\ if preferred, resulting in "L:\EPOD\...".

Anw: Added Testing procedures

2013-09-18T09:14:47Z

Added Testing procedures

← Older revision		Revision as of 11:14, 18 September 2013
Line 120:		Line 120:
	* Once data has been downloaded, click '''Login''' again.		* Once data has been downloaded, click '''Login''' again.

			==Documentation==
			{{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 it's 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}} 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}} 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.

	[[Category:WI 287575 EPOD Development and Release Process\|600]]		[[Category:WI 287575 EPOD Development and Release Process\|600]]

Anw at 14:59, 6 June 2013

2013-06-06T14:59:13Z

← Older revision		Revision as of 16:59, 6 June 2013
Line 39:		Line 39:

	*On the emulator, open the File Explorer from the Start menu.		*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 '[[~~Install_on_Device~~]]'.		*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.		*Click ''File/Save State and Exit'' - this will save the emulator with the software installed.

Anw at 11:06, 12 March 2013

2013-03-12T11:06:27Z

← Older revision		Revision as of 13:06, 12 March 2013
Line 107:		Line 107:
	* Text entry can be made through the pop-up keyboard on the device window or the emulator keypad.		* 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.		* 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.
	* You can change orientation using the numeric keypad (while NOT in numlock mode), using 7 and 9 to rotate the device).
	* ESC can be used as the Back key, to clear popup dialogues, move back one screen, clear drop-down lists, etc.		* 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.		* 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:		* Notes:
	** The Tab key does NOT move the entry to the next text box - this is a Windows convention.		** The Tab key does NOT move the entry to the next text box - this is a Windows convention.

Anw: /* Application use */

2013-03-12T10:57:45Z

Application use

← Older revision		Revision as of 12:57, 12 March 2013
Line 114:		Line 114:
	** You can't copy from Windows and paste into the emulator.		** You can't copy from Windows and paste into the emulator.

	===Application ~~use~~===		===Application Use===
	* As described in http://172.198.45.54/calidus-assist/EPOD/		* As described in http://172.198.45.54/calidus-assist/EPOD/
	* Log in with your provided ''Username'' and ''Password'', then click '''Login'''.		* Log in with your provided ''Username'' and ''Password'', then click '''Login'''.

Anw: Added Android emulator setup

2013-03-12T10:54:37Z

Added Android emulator setup

@@ Line 14: / Line 14: @@
 A full [[EPOD Admin Test Plan|test plan]] exists to run through all screens and functionality.
-==PDA Client==
+==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
@@ Line 45: / Line 45: @@
 A full [[EPOD PDA Test Plan|test plan]] exists to run through all screens and functionality.
 [[Category:WI 287575 EPOD Development and Release Process|600]]

Anw: Added Test plan links

2012-04-11T07:20:47Z

Added Test plan links

← Older revision		Revision as of 09:20, 11 April 2012
Line 11:		Line 11:

	The system can be run through any modern browser.		The system can be run through any modern browser.

			A full [[EPOD Admin Test Plan\|test plan]] exists to run through all screens and functionality.

	==PDA Client==		==PDA Client==
Line 42:		Line 44:
	The emulator is now ready for use.		The emulator is now ready for use.

			A full [[EPOD PDA Test Plan\|test plan]] exists to run through all screens and functionality.

	[[Category:WI 287575 EPOD Development and Release Process\|600]]		[[Category:WI 287575 EPOD Development and Release Process\|600]]

Anw: Created page with "==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 SQLS..."

2011-10-12T07:48:30Z

Created page with "==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 SQLS..."

New page

==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.

==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 '[[Install_on_Device]]'.
*Click ''File/Save State and Exit'' - this will save the emulator with the software installed.

The emulator is now ready for use.

[[Category:WI 287575 EPOD Development and Release Process|600]]