Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #50927 > unrolled thread

Python testing tools

Back to article view | Back to comp.lang.python

Contents

  Python testing tools cutems93 <ms2597@cornell.edu> - 2013-07-19 15:56 -0700
    Re: Python testing tools Ben Finney <ben+python@benfinney.id.au> - 2013-07-20 18:11 +1000
      Re: Python testing tools cutems93 <ms2597@cornell.edu> - 2013-07-23 10:51 -0700
        Re: Python testing tools Skip Montanaro <skip@pobox.com> - 2013-07-23 13:04 -0500
          Re: Python testing tools cutems93 <ms2597@cornell.edu> - 2013-07-23 11:12 -0700
            Re: Python testing tools Skip Montanaro <skip@pobox.com> - 2013-07-23 13:33 -0500
              Re: Python testing tools cutems93 <ms2597@cornell.edu> - 2013-07-23 11:56 -0700
                Re: Python testing tools Skip Montanaro <skip@pobox.com> - 2013-07-23 14:11 -0500
        Re: Python testing tools Ben Finney <ben+python@benfinney.id.au> - 2013-07-24 08:51 +1000
          Re: Python testing tools cutems93 <ms2597@cornell.edu> - 2013-07-30 17:18 -0700
    Re: Python testing tools Y Yen <srcmap.y.yen@gmail.com> - 2013-07-24 15:02 -0700

#50927 — Python testing tools

I am currently doing some research on testing software for Python. I found that there are many different types of testing tools. These are what I've found.

1.Unit test	
2.Mock test
3.Fuzz test
4.Web test
5.Acceptance/business logic test
6.GUI test
7.Source code checking
8.Code coverage
9.Continuous integration
10.Automatic test runners
11.Test fixtures

I know web and GUI testing tools are for specific uses. For instance, if you are not working with GUI or web pages, you don't need those testing tools. Other than these two, do you use all of the other nine testing tools? I think many of you are using unit testing tools, such as unittest and doctest, and source code checking tools, like pylint or pychecker. Do you guys use #2,3,5,8,9,10 and 11 often?

Thanks!

-Min S.

[toc] | [next] | [standalone]

#50954

cutems93 <ms2597@cornell.edu> writes:

> I am currently doing some research on testing software for Python. I
> found that there are many different types of testing tools. These are
> what I've found.

You will find these discussed at the Python Testing Tools Taxonomy
<URL:http://wiki.python.org/moin/PythonTestingToolsTaxonomy>.

Hope that helps.

[toc] | [prev] | [next] | [standalone]

#51093

On Saturday, July 20, 2013 1:11:12 AM UTC-7, Ben Finney wrote:
> cutems93 <ms2597@cornell.edu> writes:
> 
> 
> 
> > I am currently doing some research on testing software for Python. I
> 
> > found that there are many different types of testing tools. These are
> 
> > what I've found.
> 
> 
> 
> You will find these discussed at the Python Testing Tools Taxonomy
> 
> <URL:http://wiki.python.org/moin/PythonTestingToolsTaxonomy>.
> 
> 
> 
> Hope that helps.

Thank you, but I already read this page before I posted this question. What I want to know is whether you personally use these tools other than unit testing tools. 

[toc] | [prev] | [next] | [standalone]

#51094

> Thank you, but I already read this page before I posted this question. What I want to
> know is whether you personally use these tools other than unit testing tools.

I tried using one of the mock tools a few years ago.  I found it
didn't fit my brain very well.  (Maybe it was just me.)

I use pylint all the time, and coverage from time-to-time, have used
nose in the past, but not for my current stuff.  All are worth your
time.

Skip

[toc] | [prev] | [next] | [standalone]

#51095

On Tuesday, July 23, 2013 11:04:23 AM UTC-7, Skip Montanaro wrote:
> > Thank you, but I already read this page before I posted this question. What I want to
> 
> > know is whether you personally use these tools other than unit testing tools.
> 
> 
> 
> I tried using one of the mock tools a few years ago.  I found it
> 
> didn't fit my brain very well.  (Maybe it was just me.)
> 
> 
> 
> I use pylint all the time, and coverage from time-to-time, have used
> 
> nose in the past, but not for my current stuff.  All are worth your
> 
> time.
> 
> 
> 
> Skip

Thank you! What tool do you use for coverage? And have you used pychecker? I heard it is as good as pylint. What do you think?

-Min S.

[toc] | [prev] | [next] | [standalone]

#51096

> Thank you! What tool do you use for coverage?

coverage. :-)

> And have you used pychecker?

Yes, in fact, I used to use a wrapper script I wrote that ran both
pylint and pychecker, then massaged the output into
suitable-for-emacs-next-error-command

> I heard it is as good as pylint. What do you think?

They overlap a fair bit, but do somewhat different things.

S

[toc] | [prev] | [next] | [standalone]

#51097

On Tuesday, July 23, 2013 11:33:10 AM UTC-7, Skip Montanaro wrote:
> > Thank you! What tool do you use for coverage?
> 
> 
> 
> coverage. :-)
> 
> 
> 
> > And have you used pychecker?
> 
> 
> 
> Yes, in fact, I used to use a wrapper script I wrote that ran both
> 
> pylint and pychecker, then massaged the output into
> 
> suitable-for-emacs-next-error-command
> 
> 
> 
> > I heard it is as good as pylint. What do you think?
> 
> 
> 
> They overlap a fair bit, but do somewhat different things.
> 
> 
> 
> S

Could you please elaborate on the difference of the two? I heard pylint does not import your source code when it is analyzing, while pychecker does. Does that make some difference? Moreover, do you personally like pylint or pycheker and why?

Thank you!!

-Min S.

[toc] | [prev] | [next] | [standalone]

#51098

> Could you please elaborate on the difference of the two? I heard pylint
> does not import your source code when it is analyzing, while pychecker does.
> Does that make some difference? Moreover, do you personally like pylint or
> pycheker and why?

I haven't followed pychecker development for awhile.  Pylint seems
more actively maintained, though I could be wrong.  The import issue
is one significant difference, important if you are trying to check
scripts which have side effects when imported.

It's not a matter of like or not.  I use what works and can easily be
fit into the way I work.  Both pylint and pychecker satisfy that
constraint.

S

[toc] | [prev] | [next] | [standalone]

#51106

cutems93 <ms2597@cornell.edu> writes:

> On Saturday, July 20, 2013 1:11:12 AM UTC-7, Ben Finney wrote:
> > You will find these discussed at the Python Testing Tools Taxonomy
> > <URL:http://wiki.python.org/moin/PythonTestingToolsTaxonomy>.
> > 
> > Hope that helps.
>
> Thank you, but I already read this page before I posted this question.

(You will benefit from also reading and applying
<URL:http://wiki.python.org/moin/GoogleGroupsPython> before using Google
Groups. My advice: choose a different interface to this forum, Google
Groups is terrible.)

> What I want to know is whether you personally use these tools other
> than unit testing tools.

Yes, I do :-)

What are you actually wanting to learn, beyond a collection of “this is
what I use” stories?

-- 
 \      “The way to build large Python applications is to componentize |
  `\             and loosely-couple the hell out of everything.” —Aahz |
_o__)                                                                  |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#51613

On Tuesday, July 23, 2013 3:51:00 PM UTC-7, Ben Finney wrote:
> cutems93 <ms2597@cornell.edu> writes:
> 
> 
> 
> > On Saturday, July 20, 2013 1:11:12 AM UTC-7, Ben Finney wrote:
> 
> > > You will find these discussed at the Python Testing Tools Taxonomy
> 
> > > <URL:http://wiki.python.org/moin/PythonTestingToolsTaxonomy>.
> 
> > > 
> 
> > > Hope that helps.
> 
> >
> 
> > Thank you, but I already read this page before I posted this question.
> 
> 
> 
> (You will benefit from also reading and applying
> 
> <URL:http://wiki.python.org/moin/GoogleGroupsPython> before using Google
> 
> Groups. My advice: choose a different interface to this forum, Google
> 
> Groups is terrible.)
> 
> 
> 
> > What I want to know is whether you personally use these tools other
> 
> > than unit testing tools.
> 
> 
> 
> Yes, I do :-)
> 
> 
> 
> What are you actually wanting to learn, beyond a collection of “this is
> 
> what I use” stories?
> 
> 
> 
> -- 
> 
>  \      “The way to build large Python applications is to componentize |
> 
>   `\             and loosely-couple the hell out of everything.” —Aahz |
> 
> _o__)                                                                  |
> 
> Ben Finney

Sorry, I didn't notice that there are new replies. I want to know why you are using other software than unittest. Are those software more like "options" or "necessities" for you?

Thank you!
Min S.

[toc] | [prev] | [next] | [standalone]

#51169

On Friday, July 19, 2013 3:56:24 PM UTC-7, cutems93 wrote:
> I am currently doing some research on testing software for Python. I found that there are many different types of testing tools. These are what I've found.
> 
> 
> 
> 1.Unit test	
> 
> 2.Mock test
> 
> 3.Fuzz test
> 
> 4.Web test
> 
> 5.Acceptance/business logic test
> 
> 6.GUI test
> 
> 7.Source code checking
> 
> 8.Code coverage
> 
> 9.Continuous integration
> 
> 10.Automatic test runners
> 
> 11.Test fixtures
> 
> 
> 
> I know web and GUI testing tools are for specific uses. For instance, if you are not working with GUI or web pages, you don't need those testing tools. Other than these two, do you use all of the other nine testing tools? I think many of you are using unit testing tools, such as unittest and doctest, and source code checking tools, like pylint or pychecker. Do you guys use #2,3,5,8,9,10 and 11 often?
> 
> 
> 
> Thanks!
> 
> 
> 
> -Min S.

I found the python's unittest framework lack good reporting tools. 

For my project (www.srcmap.com), I want something that does high level features integration tests, scriptable, generate report in HTML table format that label pass ->Green, fail -> Red.   Separate by scripts, commands runs, etc.

  In python, it is so trivial to write you own.  It parse the json test scripts and execute the commands inside one at a time.  It works very well. 

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web