Re: How to develop my career on software testing?

> > And according to my experience, automated testing always means high
> > effort. Especially for UI testing, those public record/playback tools
> > are even unusefulness.What are your opinions?
>
> The ultimate goal of testing is the ability to write a test before writing
> the tested code, such that the test constrains the code to only perform as
> the test permits.
>
I think you mean test driven developement, but is it a problem of the
whole development process?What the testers can do to achieve the goal?

> That is a goal. Write many tests like that, but not all. If you don't
> acheive the goal, then neither side of testing (first and last) will work.
>
> GUIs have a side only users see or touch. Most commercial "GUI Testing"
> tools emulate a user. This makes writing new test cases that force
> predictable changes in GUIs very hard. That, in turn, leads to tests that
> break too easily.
>
> Most business GUIs need only treat a GUI Toolkit as "just another library".
> Developers should write test cases that drive a GUI without displaying it.

I think what you described is a ideal GUI software architecture and
developement situation.Most projects I know don't fulfill it.No test
API for testers, only one way to do test:manual test.

> GUI Toolkits support an in-memory representation that simulates its screen
> appearance and behavior. Tests can query that back, if they use the same
> language and modules as the application. Developers should constantly
> monitor the real GUIs appearance, to prevent tests from misleading. Some
> GUIs can Set a value without providing the ability to Get that value back
> accurately. Developers should spot mismatches, and increase the test-side
> code to build an alternate and more accurate Get, and use that in all tests.
> Frequently reviewing the GUI while writing it, under test, should increase
> the odds of not needing to review the GUI while making graphical changes.
>

I could get that what you said is the trend of software development,
and the improvement of the whole process.But I still confused that how
I could do under current situation, testers have little power and is
hard to be involed in other phases,how we could require developers to
improve theire architeture from test driven point of view?And I think,
it's a big system engineering for those established process, need
involve all roles.

And me, it's just a tester who want to improve testing konwledge and
skills, have no power current, what I could do? that's my confusion
now.

> --
> Phlip
> http://www.greencheese.org/ZeekLand <-- NOT a blog!!!

.

Relevant Pages

  • Re: What is the BEST WAY to write test cases?
    ... attach different risks to the usecases ... and then write tests onwards.For writing tests, ... For other testers, you might want to be more specific ("Use the ... Could this be a solution i.e. list down all GUI ...
    (comp.software.testing)
  • Re: Tile frame widget
    ... the Tile stuff has not reached the point of a serious ... But the Real World point is that you do *not* need to use themed widgets ... in your GUI. ... developers so choose to do so. ...
    (comp.lang.tcl)
  • Re: vs 2005 gui ide
    ... Most experienced asp.net developers I know ... Or if they use the ASP editor most of the time. ... Coming from the VB6 environment (and probably the VB.NET (windows app), it is extremely easy to manipulate the gui and get what you want. ...
    (microsoft.public.dotnet.general)
  • Re: How to develop my career on software testing?
    ... Most commercial "GUI Testing" ... This makes writing new test cases that force ... > Developers should write test cases that drive a GUI without displaying it. ... API for testers, only one way to do test:manual test. ...
    (comp.software.testing)
  • Re: Mac OS X and Linux
    ... B> developers would have to do is to re-code the GUI stuff. ... MacOSX does not run a UNIX-style X11 system as *the* GUI ... probably a collection of libraries to support 'legacy' applications. ...
    (comp.os.linux.misc)