qa

We have a pretty complex Java system which includes a few back-end tiers including a database and a proprietary Swing front-end. There are back-end APIs to which external parties can attach that mimic our front-end. There are approximately 5 silos within our org that share this system. In total there are around 15 developers maintaining this system. Is there a rule of thumb on what the size our QA team should be? Edit: To add a bit of context based on questions raised in the responses thus far: We have about four major releases a year, and a bunch of minor ones in between. Our platform has

Currently, I am writing the automation testing using java and selenium rc. I would like to verify all the contents present on the user interface, the function is ie below: public String UITest() throws IOException { String result="Test Start<br />"; try { openfile(1); for (String url : uiMaps.keySet()) { selenium.open(url); for (String item : uiMaps.get(url)) { assertEquals(url+" check: " + item, true,selenium.isTextPresent(item)); result+=url+" check: " + item+" : OK<br />"; } } } catch (AssertionError e) { result+=e.getMessage(); } result+="Test finished<br />"; return result; } the function

What are the best processes with for Quality Assurance (aside from testing)? Do you use code reviews, code profilers? Do you use a QA Standards document, or just eyeball code? Also how do you provide feedback to the developers? What do YOU do for QA? Jay Bazuzi Unless you have a very low issue rate, use a database to track issue. Make the QA process interesting by getting developers to do TDD ( Test-Driven Development ). It's good for them, and it gets rid of the stupid bugs. Automate tests. Get QA involved in the product from the beginning, not just the last 2 weeks. Give them power. QA gets

I'm writing a series of automated, end-to-end test cases that exercise a RestFUL API. I have several good test scripts, written in Groovy, that provide the sort of tests and build the confidence we need, and we're looking at integrating these into a nightly build, as well as allow the QA team to run them. This is a step above Unit testing, as we are looking at complete end-to-end workflows, rather than atomic steps. The output is currently human readable, with each test condition printing out a line which defines the test, the value being read, and a true/false to show if the test condition