Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SWTBot/Troubleshooting"
< SWTBot
m |
m (using templates for creating links) |
||
| Line 1: | Line 1: | ||
| + | {{SWTBot}} | ||
| + | |||
===SWTBot fails with"swtbottestapplication" could not be found in the registry=== | ===SWTBot fails with"swtbottestapplication" could not be found in the registry=== | ||
| Line 8: | Line 10: | ||
Then the most common cause is that the target platform does not have the "org.eclipse.swtbot.eclipse.core" plugin. If you're certain that you have this plugin, but the error persists. Try running with -consoleLog -debug options turned on while running the tests. This would most probably tell you about a missing dependency that causes the plugin to not load. | Then the most common cause is that the target platform does not have the "org.eclipse.swtbot.eclipse.core" plugin. If you're certain that you have this plugin, but the error persists. Try running with -consoleLog -debug options turned on while running the tests. This would most probably tell you about a missing dependency that causes the plugin to not load. | ||
| − | |||
| − | |||
Revision as of 03:29, 1 July 2009
| SWTBot |
| Website |
| Update Sites |
| Community |
| Mailing List |
| Forums/Newsgroups |
| IRC |
| Contribute |
| Open Bugzilla tickets |
| Open Gerrit reviews |
| Browse Source |
| Continuous Integration |
SWTBot fails with"swtbottestapplication" could not be found in the registry
If you get an error like:
java.lang.RuntimeException: Application "org.eclipse.swtbot.eclipse.core.swtbottestapplication" could not be found in the registry. The applications available are: some.long.list.of.application.ids
Then the most common cause is that the target platform does not have the "org.eclipse.swtbot.eclipse.core" plugin. If you're certain that you have this plugin, but the error persists. Try running with -consoleLog -debug options turned on while running the tests. This would most probably tell you about a missing dependency that causes the plugin to not load.