1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 <meta name="generator" content="Movable Type 5.2.3" />
8 <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9 <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10 <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
12 <title>Status for Andrew DeFaria: EAST Automation</title>
14 <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15 <link rel="prev" href="http://defaria.com/blogs/Status/archives/000700.html" title="Sharable vs Non-sharable derived objects" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/000702.html" title="Migrating colocated views from 6.0 -> 7.0" />
19 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
20 xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
21 xmlns:dc="http://purl.org/dc/elements/1.1/">
23 rdf:about="http://defaria.com/blogs/Status/archives/000701.html"
24 trackback:ping="http://defaria.com/mt/mt-tb.cgi/88"
25 dc:title="EAST Automation"
26 dc:identifier="http://defaria.com/blogs/Status/archives/000701.html"
27 dc:subject="General Dynamics"
28 dc:description="What's been done The EAST test automation tool rantest currently can run properly formated EAST tests. By properly formated we mean that they 1) run to completion and 2) report a status in their log file. Logfile collection for EAST..."
30 dc:date="2008-03-27T10:30:05-06:00" />
37 <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
39 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
41 <div id="container-inner" class="pkg">
44 <div id="banner-inner" class="pkg">
45 <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
46 <h2 id="banner-description">Searchable status reports and work log</h2>
51 <div id="pagebody-inner" class="pkg">
53 <div id="alpha-inner" class="pkg">
55 <p class="content-nav">
56 <a href="http://defaria.com/blogs/Status/archives/000700.html">« Sharable vs Non-sharable derived objects</a> |
57 <a href="http://defaria.com/blogs/Status/">Main</a>
58 | <a href="http://defaria.com/blogs/Status/archives/000702.html">Migrating colocated views from 6.0 -> 7.0 »</a>
62 <div class="entry" id="entry-701">
63 <h3 class="entry-header">EAST Automation</h3>
64 <div class="entry-content">
65 <div class="entry-body">
66 <h3>What's been done</h3>
69 <li>The EAST test automation tool rantest currently can run <i>properly
70 formated</i> EAST tests. By <i>properly formated</i> we mean that they
71 1) run to completion and 2) report a status in their log file.</li>
73 <li>Logfile collection for EAST tests is performed and a tar file,
74 EASTLogs.tgz, is created and if run for record (-rfr) specified that
75 log file will be checked in (coded but untested - see below).</li>
77 <li>Many tests can be run in succession using the -file option and
78 specifying multiple tests in the file (See <a
79 href="http://ranweb/dokuwiki/doku.php?id=ran:rantest">rantest</a> wiki
82 <li>A rudimentary conditional test execution facility exists. For
83 example, testers can name tests then refer to them in a subsequent test
84 with an "if" statement so as to say "run this test if <named
85 test> passed (See <a
86 href="http://ranweb/dokuwiki/doku.php?id=ran:rantest">rantest</a> wiki
89 <li>A facility for running test in the background has been
90 implemented as some EAST test script must run in the background while
91 other tests run simultaneously.</li>
93 <li>A crude rendezvous system has been implemented such that rantest
94 will poll the logfile looking for a rendezvous string that will
95 indicate to rantest that the backgrounded test has reached a certain
96 point and it's OK to proceed with other tests.</li>
98 <li>Logging of what rantest does has been implemented.</li>
100 <li>A crude -script test option has been implemented that allows
101 rantest to "farm out" the verification of a test for tests that
102 require more complex verification. Any script can be coded. The only
103 requirement is that it reports success or failure through it's exit
106 <li>Worked on learning moshell as some verifications require
109 <li>Implemented a simple case of verifying that a cell is set up (a
110 manual verification step for Sim Cell Setup of preSWIT).</li>
112 <li>Ngan has created test profiles and Ross Wilson says that we are
113 going to run these test profiles through rantest this afternoon.</li>
115 <li>Documented most of <a
116 href="http://ranweb/dokuwiki/doku.php?id=ran:rantest">rantest</a>'s
117 usage on the wiki.</li>
119 <li>Ross and Gantry have created Perl scripts and TPL's such that an
120 EAST test can drive a TM500. While rantest can run such tests it needs
121 to be taught how to gather the TM500 log files produced.</li>
124 <h3>What we're impeded on</h3>
127 <li>I believe many of the SWIT tests are not currently properly
128 formatted. Such tests will need to be altered before they can be truly
129 automated through rantest</li>
131 <li>WRT preSWIT testing, I need Leslie to modify her tests to
132 properly write rendezvous strings in SIM Cell Setup so that rendezvous
133 can work and sanity/preSWIT testing can proceed.</li>
135 <li>Gather tests from Ngan (and others) </li>
137 <li>We often don't have time on the various RNC's/etc. to perform
138 testing. Some tests, i.e. SIM Cell Setup, are interruptive of other
139 EAST engineer's work.</li>
141 <li>Moshell is crude, picky and buggy and... not supported by Ericson!</li>
147 <li>Create run for record view and test out -rfr checkin
150 <li>Get EAST/TM500 test to work (currently failing) so as to
151 check/modify TM500 logfile creation</li>
153 <li>Get EAST/NMS test to work (currently non-existant?) so as to
154 check/modify NMS logfile creation.</li>
156 <li>Implement XML parsing to determine whether or not we have TM500
157 logs or NMS logs to collect. Either that or get Gantry to change the
158 format of the message indicating where the logfile is to include what
159 type of logfile it is.</li>
161 <li>Once Leslie modifies tests for rendezvous, attempt sanity again
162 and add in the -script "IsCellUp <machine> <cell>"
165 <li>Bob wants us to write a simple and a complex example of test
166 verification. Based on Doug Elder's <i>How to Analyze rnc</i>
167 document, implement it's verification steps which get progressively
168 more complex. The IsCellUp script can also serve as an example
169 verification script.</li>
173 <div id="more" class="entry-more">
177 <p class="entry-footer">
178 <span class="post-footers">Posted by on March 27, 2008 10:30 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000701.html">Permalink</a>
183 <div class="trackbacks">
184 <h3 id="trackback" class="trackbacks-header">TrackBack</h3>
185 <div id="trackbacks-info">
186 <p>TrackBack URL for this entry:<br />http://defaria.com/mt/mt-tb.cgi/88</p>
188 <div class="trackbacks-content">