|
sl@0
|
1 |
How To Run TNETDB test case manually (Windows Environment)
|
|
sl@0
|
2 |
|
|
sl@0
|
3 |
(1) One has to replace epoc.ini (this epoc.ini was provided by Networking team) file which has WIN_TUNNEL field.
|
|
sl@0
|
4 |
This field has networking test network IP address and port number.
|
|
sl@0
|
5 |
|
|
sl@0
|
6 |
(2) One has to build //PR/share/DABSRelease/buildtools/wintunnel/eka2/wins/... component.
|
|
sl@0
|
7 |
So that wintunnel application will redirect the HostResolver request to Networking Test Network.
|
|
sl@0
|
8 |
|
|
sl@0
|
9 |
How To Run TNETDB test case manually (Hardware)
|
|
sl@0
|
10 |
|
|
sl@0
|
11 |
(1) Include StdLibTests.iby at the time of building ROM.
|
|
sl@0
|
12 |
(2) Start TCP2SER application in the PC to which H2/H4 hardware is connected.
|
|
sl@0
|
13 |
Please refer to (http://loncoredev01.intra/twiki/bin/view/ToolsAndUtilities/TCP2SerTool) link for further detail.
|
|
sl@0
|
14 |
(3) In the hardware, go to z:\test directory and run TNETDB. Before running TNETDB, TCP2SER must be started as that
|
|
sl@0
|
15 |
application will be responsible for re-directing the request to Test Network.
|
|
sl@0
|
16 |
|
|
sl@0
|
17 |
NOTE: The above epoc.ini (which has WINTUNNEL info) and wintunnel application are needed at the time of testing in Emulator but not in hardware.
|
|
sl@0
|
18 |
At the time of testing in hardware TCP2SER will be used in place of wintunnel.
|
|
sl@0
|
19 |
|
|
sl@0
|
20 |
Why use Networking Test Environment ?
|
|
sl@0
|
21 |
|
|
sl@0
|
22 |
GetHostByName and GetHostByAddr uses RHostResolver class which internally sends the request to internet to get the info.
|
|
sl@0
|
23 |
But networking team is using their own test environment to simulate above things. As we are calling their functions to
|
|
sl@0
|
24 |
do our stuff we need their environment too.
|
|
sl@0
|
25 |
|
|
sl@0
|
26 |
GetHostByName and GetHostByAddr might return multiple host names for a single address or
|
|
sl@0
|
27 |
multiple addresses for a single host name. All these Host reolve info was stored in their
|
|
sl@0
|
28 |
test environment. So it is easy to test and compare the test result as the addresses were not changed.
|
|
sl@0
|
29 |
|
|
sl@0
|
30 |
Few Reasons TNETDB might fail.
|
|
sl@0
|
31 |
|
|
sl@0
|
32 |
(1) In the test code, addresses and host names are hard-coded. So check wheter the test is failing
|
|
sl@0
|
33 |
at the the time of comparing the results. It might be due to change of addresses and host names in test database.
|
|
sl@0
|
34 |
|
|
sl@0
|
35 |
If you are testing in Emulator:
|
|
sl@0
|
36 |
|
|
sl@0
|
37 |
(2) As epoc.ini was copied once from networking team. Cross check whether epoc.ini file is still relevant or not.
|
|
sl@0
|
38 |
Or Networking team has changed their testing strategy. (As this test case is closely associated with networking test environment).
|
|
sl@0
|
39 |
|
|
sl@0
|
40 |
If you are testing in Hardware:
|
|
sl@0
|
41 |
|
|
sl@0
|
42 |
(2) Check whether you have correct config.xml file in TCP2SER directory. For detail please refer to
|
|
sl@0
|
43 |
http://loncoredev01.intra/twiki/bin/view/ToolsAndUtilities/TCP2SerTool
|