From: Elliot Smith <elliot.smith@intel.com>
To: toaster@yoctoproject.org
Subject: [PATCH 1/2][v2] toaster-tests: remove click on disabled element in test
Date: Fri, 17 Jun 2016 16:49:11 +0100 [thread overview]
Message-ID: <1466178552-3642-1-git-send-email-elliot.smith@intel.com> (raw)
On Firefox 47, attempting to click on the "Submit" button in
the test which attempts to create a project with a duplicate name
fails, as the button is not enabled if the name is a duplicate. This
also causes the test to fail.
Remove the call to the click() method which causes the test to fail.
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
---
bitbake/lib/toaster/tests/browser/test_new_project_page.py | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/bitbake/lib/toaster/tests/browser/test_new_project_page.py b/bitbake/lib/toaster/tests/browser/test_new_project_page.py
index 1b038ac..180a690 100644
--- a/bitbake/lib/toaster/tests/browser/test_new_project_page.py
+++ b/bitbake/lib/toaster/tests/browser/test_new_project_page.py
@@ -80,7 +80,7 @@ class TestNewProjectPage(SeleniumTestCase):
"""
Should not be able to create a new project whose name is the same
as an existing project
- """
+ """
project_name = "dupproject"
@@ -100,10 +100,6 @@ class TestNewProjectPage(SeleniumTestCase):
self.assertTrue(("Project names must be unique" in element.text),
"Did not find unique project name error message")
- # Try and click it anyway, if it submits we'll have a new project in
- # the db and assert then
- self.click("#create-project-button")
-
self.assertTrue(
(Project.objects.filter(name=project_name).count() == 1),
- "New project not found in database")
+ "New project not found in database")
\ No newline at end of file
--
2.7.4
next reply other threads:[~2016-06-17 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:49 Elliot Smith [this message]
2016-06-17 15:49 ` [PATCH 2/2][v2] toaster-tests: define capabilities for latest Firefox driver Elliot Smith
2016-06-17 17:53 ` Michael Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1466178552-3642-1-git-send-email-elliot.smith@intel.com \
--to=elliot.smith@intel.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.