You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a bunch of "Should Contain" keywords for tables (Table Should Contain, Table Should Not Contain, ....) For all of them also a "Should Not Contain" version should exist.
(Of course you can use a workaround, e.g.
Run Keyword And Expect Error Table identified by 'xpath=.//table[@id='credentialList:dataTable']' should have contained text 'HTTP Access'. selLib.Table Should Contain xpath=.//table[@id='credentialList:dataTable'] HTTP Access loglevel=NONE
I am aware of the solution and I can implement that easily. however I don't want to start working on it without assigning a ticket to myself.
just wanted to confirm with @zephraph as well, if he hasn't started working on it and if he can assign the ticket to me, I can start working on it right away.
I haven't heard that anyone would be working on the request. Nor I haven't seen pull request.
The Feature Request label doesn't mean that someone would be working on the matter. It means, more or less, that idea behind the request is OK and if the code in the pull request is good, it can be merged to the master. This way it will go to the next release.
I think that now one from the core team has worked on the matter. So if you want to send it, please feel free to do so.
So,
the issue was opened in 2015...
a PR was submitted in 2017...
which was ignored until 2018...
resubmitted in 2018...
and then closed (wrongly) because of "inactivity" in 2019...
Activity
just-be-dev commentedon Jul 24, 2015
Easy enough, I'll add it to the todo list.
Gaurang033 commentedon Mar 5, 2016
Hi @zephraph
I am willing to work on it, if you haven't started it yet.
tarand commentedon Mar 7, 2016
Hi Shah,
thanks!
No, I did not start work on it until now (except that I have a private robot keyword for that…) But I guess the solution will be done on python side?
Ciao
Thomas
Thomas Arand
Tel. +49 (89) 5159 36328 / +49 (160) 90888023 / (Soft) 8041034
thomas.arand@nokia.commailto:thomas.arand@nokia.com
From: EXT Gaurang Shah [mailto:notifications@github.com]
Sent: Saturday, March 05, 2016 5:37 PM
To: robotframework/Selenium2Library Selenium2Library@noreply.github.com
Cc: Arand, Thomas (Nokia - DE/Munich) thomas.arand@nokia.com
Subject: Re: [Selenium2Library] Need "Table Should Not Contain" keyword (#463)
I am willing to work on it, if you haven't started it yet.
—
Reply to this email directly or view it on GitHubhttps://github.com/robotframework/Selenium2Library/issues/463#issuecomment-192681879.
Gaurang033 commentedon Mar 7, 2016
Hi @tarand
I am aware of the solution and I can implement that easily. however I don't want to start working on it without assigning a ticket to myself.
just wanted to confirm with @zephraph as well, if he hasn't started working on it and if he can assign the ticket to me, I can start working on it right away.
aaltat commentedon Mar 7, 2016
I haven't heard that anyone would be working on the request. Nor I haven't seen pull request.
The Feature Request label doesn't mean that someone would be working on the matter. It means, more or less, that idea behind the request is OK and if the code in the pull request is good, it can be merged to the master. This way it will go to the next release.
I think that now one from the core team has worked on the matter. So if you want to send it, please feel free to do so.
Added following keywords and their acceptance test cases to fix the i…
Added following keywords and their acceptance test cases to fix the i…
Added following keywords and their acceptance test cases to fix the i…
eL-Prova commentedon Feb 25, 2017
@aaltat @Gaurang033
https://github.com/robotframework/Selenium2Library/pull/767
jimpriest commentedon Jul 25, 2018
Will this ever be integrated?
aaltat commentedon Jul 26, 2018
No-one has seen the feature important enough to implement it. If you need it, please send a PR.
eL-Prova commentedon Jul 26, 2018
I have implemented long time ago (see my pull). Because of renaming not found but link is:
#767
Pull again submitted
aaltat commentedon May 15, 2019
Closing due inactivity. If there is an interest to me this happen please open new issue and preferably create also a PR
RH-sdavey commentedon Nov 3, 2022
So,
the issue was opened in 2015...
a PR was submitted in 2017...
which was ignored until 2018...
resubmitted in 2018...
and then closed (wrongly) because of "inactivity" in 2019...
And now Im looking for the same thing in 2022.
emanlove commentedon Nov 5, 2022
Looking at the pull request there were many requested changes that were not completed. I believe that was why it was closed out.