Closed GoogleCodeExporter closed 9 years ago
I think I'm experiening the same problem, I did a little research and seems
like if
sometimes in the class JComboBoxDriver the value in the list is compared
againest the
actual object (which I doing a GUI test shouldn't even know) and in other
methods
it's compared againest the right value also represented in the combo box.
For example if I require a selection
org.fest.swing.driver.JComboBoxDriver.requireSelection(JComboBox, String), I
would
have to require the selection 'Olala'. But to select the item 'Olala' I might
have to
select an object. In my opinion in the method
org.fest.swing.driver.JComboBoxDriver.selectItem(JComboBox, Object) the
comparision
be changed from
if (areEqual(itemAt(comboBox, i), value)) {
to
if (areEqual(value(comboBox, i), value)) {
In my opinion if I'm testing the GUI and want to select the item 'Olala', I
can't
know the object behind this item. The end-user neither knows it.
Original comment by matthi...@gmail.com
on 28 May 2008 at 7:20
Hi Mattias,
You are right. We were comparing to the value in the model instead of using the
cell
reader. I just checked-in a fix :)
Best regards,
-Alex.
Original comment by Alex.Rui...@gmail.com
on 28 May 2008 at 3:57
Set the module as a label, instead of being part of the title.
Original comment by Alex.Rui...@gmail.com
on 1 Dec 2008 at 1:59
Original issue reported on code.google.com by
Alex.Rui...@gmail.com
on 27 May 2008 at 4:28