search

yanne / api-testing

I am using this to test GitHub API
1 stars 0 forks source link

Find unused User Keywords #374

Closed yanne closed 9 years ago

yanne commented 9 years ago

Originally submitted to Google Code by @yanne on 1 Sep 2008

It should be possible to search for unused keywords in test case and resource files

yanne commented 9 years ago

Originally submitted to Google Code by @pekkaklarck on 26 Jan 2009

Showing warnings and errods like this requires some special UI. Even though that would be a really nice feature, it's out of the scope of 1.0 version.

yanne commented 9 years ago

Originally submitted to Google Code by @yanne on 21 Oct 2010

Most of the functionality required by this feature has been implemented as part of keyword rename ( issue 14 ).

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 4 Nov 2010

I suggest that this should be done in background and not with a special UI tool that has to be executed from some menu from somewhere that no-one can find.

Most likely this would have to be lazy - so that you have to first open an editor view of the file that contains the keyword to get this finding started.

At least user keywords in test case files are easy as they can be used only in that specific file.

yanne commented 9 years ago

Originally submitted to Google Code by @pekkaklarck on 4 Nov 2010

I would like to have:

1) Number of how many time user keyword has been used in the keyword editor. There should be also possibility to navigate to those places somehow.

2) A column in keyword search indicating how many times a kw has been used, again with some navigation possibility. It should be possible to sort kws using this column, which would make it trivial to find kws with zero usages.

yanne commented 9 years ago

Originally submitted to Google Code by @jrantanen on 14 Dec 2010

Descoped

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 31 Dec 2010

After finally figuring out what GIL really does I am kind of skeptic about how easy this feature is to implement. Most likely this feature needs to have multiple processes running to make it run nicely in the background (I so want to implement this!!!).

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 13 Feb 2012

Making a release with the currently done set of features and bug fixes.

==> Moving others

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 20 Feb 2012

Some notes about current version ( https://github.com/robotframework/RIDE/commit/46afe2d0d7ce5f0bb00b25307ed4994c3ba86d7b ): 1) There is no feedback if the search is executed with a very small test set without unused keywords -- Should somehow indicate that the search has finished 2) Should clean search results at least when a new project / suite is opened in RIDE