Skip to content

Need "Table Should Not Contain" keyword #463

Closed

Description

@tarand

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

But this is obviously very ugly)

Activity

  1. just-be-dev commented on Jul 24, 2015

    @just-be-dev
    Contributor

    Easy enough, I'll add it to the todo list.

  2. Gaurang033 commented on Mar 5, 2016

    @Gaurang033
    Contributor

    Hi @zephraph
    I am willing to work on it, if you haven't started it yet.

  3. tarand commented on Mar 7, 2016

    @tarand
    Author

    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.

  4. Gaurang033 commented on Mar 7, 2016

    @Gaurang033
    Contributor

    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.

  5. aaltat commented on Mar 7, 2016

    @aaltat
    Contributor

    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.

  6. added this to the milestone on Feb 1, 2017
  7. modified the milestones: , on May 22, 2017
  8. jimpriest commented on Jul 25, 2018

    @jimpriest

    Will this ever be integrated?

  9. aaltat commented on Jul 26, 2018

    @aaltat
    Contributor

    No-one has seen the feature important enough to implement it. If you need it, please send a PR.

  10. eL-Prova commented on Jul 26, 2018

    @eL-Prova

    I have implemented long time ago (see my pull). Because of renaming not found but link is:
    #767

    Pull again submitted

  11. removed this from the milestone on Sep 13, 2018
  12. aaltat commented on May 15, 2019

    @aaltat
    Contributor

    Closing due inactivity. If there is an interest to me this happen please open new issue and preferably create also a PR

  13. RH-sdavey commented on Nov 3, 2022

    @RH-sdavey

    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.

  14. emanlove commented on Nov 5, 2022

    @emanlove
    Member

    Looking at the pull request there were many requested changes that were not completed. I believe that was why it was closed out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions