While I am writing test cases. At the time of testing I am facing an issue.
Hi all. Below is my test case code in bdd python. So here I have written the test cases and everything is working fine But i am facing an issue with this error 1. selenium.common.exceptions.ElementNotInteractableException: Message: element not interactable (Session info: chrome=94.0.4606.54) *here is my code* *.test.feature* ``` Feature: Vikreya login Scenario: Login to vikreya with valid parameter: Given I launch chrome browser When i open vikreya web page And click on login button And enter username "aalamkazi24@gmail.com" and password "aalam@123A" And click on submit button Then user successfully login to the web site ``` *test.py* ``` from behave import * from selenium import webdriver @given('I launch chrome browser') def launch_Browser(context): context.driver = webdriver.Chrome() @when('i open vikreya web page') def open_vikreya(context): context.driver.get("http://127.0.0.1:8000/") @when('click on login button') def click_login_btn(context): context.driver.find_element_by_xpath("//body/div[1]/div[3]/button[1]").click() @when('enter username "{user}" and password "{pwd}"') def input_validate(context, user, pwd): context.driver.find_element_by_id("asadSalima").send_keys(user); context.driver.find_element_by_id("asadAlam").send_keys(pwd); @when('click on submit button') def click_submit(context): context.driver.find_element_by_xpath("//button[contains(text(),'Log In')]").click() @then('user successfully login to the web site') def success_lunch(context): text = context.driver.find_element_by_xpath("//span[contains(text(),'Welcome back! Alam')]").text assert text == "Welcome back! Alam" ```
Unable to connect to TestComplete
Hello All, I have created build on AzureDevops for TestComplete. When I run build I'm getting this error. Any idea how to fix it ? 2021-10-08T14:22:55.3900080Z##[error]Failedtogetalistoftestsfromthe"C:\agent\_work\r1\a\_TestProject\SimpleTest.pjs"fileduetothefollowingerror:UnabletoconnecttoTestComplete:Serverexecutionfailed(ExceptionfromHRESULT:0x80080005(CO_E_SERVER_EXEC_FAILURE))
BDD BeforeStep & AfterStep Hooks
Hi, I wanted to perform certain steps after every step execution of the BDD scenario. In specflow there were hooks for Before and After step but I am unable to find the same here. So, would like to know if there is anyways to get the current step name during execution which then I can pass to another method.
Get Tags associated Scenario Outline Examples programatically
Hi, Just like we can get the tags associated with a feature file inside a beforeFeature hook like "Feature.Tags.item(0)" or the tags linked with a scenario in a beforeScenario hook "Scenario.Tags.item(0)", Is it also possible to retrieve the tags associated with a Scenario Outline Example? Let's say I have a feature file as shown below: @Login Feature: AppLogin Scenario Outline: As a user, I should be able to login to XYZ application When user launches the application Then login screen should get displayed When user enters "<username>" And user enters "<password>" And user clicks on login button Then user should be able to see main screen @admin @level1 Examples: |username|password| |adm1 |paxxword| @supervisor @level1 Examples: |username|password| |sup1 |paxxword| @manager @level2 Examples: |username|password| |mgr1 |paxxword| @employee @level2 Examples: |username|password| |emp1 |paxxword| Now, if I run the above scenario for Level1 users i.e. by using the tag@level1, how do I know If the current scenario is being executed for the admin or supervisor? Somehow, I need to retrieve the value of the 1st tag associated with the Examples. Maybe something like Example.tags.item(0) but such an object does not exist in testcomplete? Can any one please help?Generate Step definition in Keyword test recorder
Hi, The feature to record directly into the step definition script and be guided by the recorder toolbar is great but is reserved to the testers that are comfortable with scripting. To be able to do the same in the Keyword test module would be very useful and open up the tool to a larger number of testers. I know you can link the script to the keyword tests but this defeats the purpose of having a sime and easy to maintain framework.
