Re: Need recommendation for Freeware Agile Testing Tools
- --- In firstname.lastname@example.org, "Thurn, Michelle CWT-MSP" <mthurn@...>
>You didn't mention whether the UI of your Java application is some kind of web browser or
> The reason for a potentially non functional UI are new pieces of
> functionality that include multiple layers of different domains. Many
> times the UI is the last piece that 'gets hooked up'. The biggest reason
a Java desktop application using AWT or Swing. In either case, I've written about some
specific free tools at the bottom of this article:
> of all is to enable QA to get involved in testing development's codeThis is a good start.
> earlier on in the Sprint cycle.
I'm disappointed no one has suggested:
1) Getting past the bogus dichotomy between "system tests" (or "functional tests") and
"unit tests." Unfortunately existing tools, roles, and legacy habits tend to reenforce this
2) Pairing "QA" (or your Scrum team member who previously developed background and
skills in testing) with "development" (the Scrum team members who previously developed
skills with coding) while writing these tests. Why are we so afraid of working together?