[OE-core] [PTACH V2] oeqa/runtime: Update test names with testopia tc numbers.

[Stoicescu, CorneliuX]

> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf
> Of Stefan Stanacar
> Sent: Monday, May 19, 2014 12:28 PM
> To: Musat, GeorgeX L
> Cc: openembedded-core at lists.openembedded.org
> Subject: Re: [OE-core] [PTACH V2] oeqa/runtime: Update test names with
> testopia tc numbers.
> 
> Hi Lucian,
> 
> On Fri, May 16, 2014 at 11:44 AM, Lucian Musat
> <georgex.l.musat at intel.com> wrote:
> >
> >  class SmartRepoTest(SmartTest):
> > @@ -54,11 +54,12 @@ class SmartRepoTest(SmartTest):
> >      @classmethod
> >      def tearDownClass(self):
> >          self.repo_server.stop()
> > +       smartsRepo = SmartRepoTest
> >
> 
> Again, this line doesn't make sense and it probably shouldn't be here.
> 
> >  class SyslogTest(oeRuntimeTest):
> >
> > -    @skipUnlessPassed("test_ssh")
> > -    def test_syslog_help(self):
> > -        (status,output) = self.target.run('/sbin/syslogd --help')
> > -        self.assertEqual(status, 0, msg="status and output: %s and %s" %
> (status,output))
> > +    @skipUnlessPassed("test_ssh_tc_224")
> > +    def test_syslog_help_tc_202(self):
> > +               (status,output) = self.target.run('/sbin/syslogd --help')
> > +               self.assertEqual(status, 0, msg="status and output: %s
> > + and %s" % (status,output))
> >
> 
> There are some whitespaces/tabs added here that probably shouldn't be.
> 
> Please also add a description why this patch is needed. Why do we need to
> add testopia numbers to test names, how is it useful?
> Also, isn't there any other way we could map these tests to testopia
> testcases?
> 

Hello Stefan,

Indeed we need a better description for this. Unfortunately there is no easy way to map these test cases without adding another maintenance point. Also this will be easy to read in the test output both by human eye and automated scripts.
What do you think? Do you have another idea we could investigate?

Regards,
Corneliu

> Cheers,
> Stefan
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core