blocks|key|743264|text|Spring+Dynamic+Modules对+testing+OSGi+bundles有很好的支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|743265|entityMap|0|LINK|mutability|MUTABLE|url|http://static.springframework.org/osgi/docs/current/reference/html/testing.html^0|N|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Spring Dynamic Modules has excellent support for <a href="http://static.springframework.org/osgi/docs/current/reference/html/testing.html" rel="noreferrer"> testing OSGi bundles</a>.

blocks|key|2974881|text|最近，你应该看看Pax+Exam：http://team.ops4j.org/wiki/display/paxexam/Pax%2BExam|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2974882|这是OPS4J目前与测试相关的工作。|2974883|entityMap|0|LINK|mutability|MUTABLE|url|http://team.ops4j.org/wiki/display/paxexam/Pax%2BExam^0|H|1F|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

More recently, you should have a look at Pax Exam:
<a href="http://team.ops4j.org/wiki/display/paxexam/Pax+Exam" rel="noreferrer">http://team.ops4j.org/wiki/display/paxexam/Pax+Exam</a>

This is the current effort at OPS4J related to testing.

blocks|key|3819169|text|以下是一些尚未提及的工具：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819170|我使用的是Tycho，这是一个使用来构建|offset|length|3819171|插件的工具。如果您在它们自己的插件或插件片段中创建测试，Tycho就可以在它自己的OSGi实例中运行每组测试，以及它所需的所有依赖项。Intro和further+info。这对于me.|unordered-list-item|3819172|jUnit4OSGI来说工作得很好，看起来很简单。您创建了OSGiTestCase的子类，并获得了像getServiceReference()这样的方法，它是一个用于Eclipse+/+OSGi插件的无头构建系统，具有名为Autotestsuite.的a+test-running+framework它在构建步骤之后，在OSGi环境的上下文中运行测试。但是，它似乎没有被维护了几年。我认为许多Eclipse项目正在从Pluginbuilder迁移到Tycho.|style|CODE|BOLD|3819173|Another，选项是在中启动一个an+OSGi容器的实例你的单元测试，你可以直接运行，如here所解释的。|3819174|是一个写了a+small+的人，它搜索JUnit+(3)测试并运行它们。|3819175|3819176|entityMap|0|LINK|mutability|MUTABLE|url|http://www.eclipse.org/tycho/|1|http://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-test-plugin|2|http://wiki.eclipse.org/Tycho/Reference_Card#Test_bundles|3|http://felix.apache.org/site/apache-felix-ipojo-junit4osgi-tutorial.html|4|http://www.pluginbuilder.org/documentation/run-tests/|5|http://www.talios.com/osgi_based_integration_testing_with_testng_and_apache_felix.htm^0|0|5|5|0|0|1V|5|1|21|C|2|0|1E|L|33|D|0|A|3|3I|O|4|0|H|I|19|4|5|0|5|7|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|F|3|G|5|H|7|1F|8|@]|9|@$D|1G|E|1H|1|1I]|$D|1J|E|1K|1|1L]]|A|$]]|$1|I|3|J|5|H|7|1M|8|@$D|1N|E|1O|K|L]|$D|1P|E|1Q|K|M]]|9|@$D|1R|E|1S|1|1T]|$D|1U|E|1V|1|1W]]|A|$]]|$1|N|3|O|5|H|7|1X|8|@$D|1Y|E|1Z|K|M]]|9|@$D|20|E|21|1|22]]|A|$]]|$1|P|3|Q|5|H|7|23|8|@$D|24|E|25|K|M]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|27|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]|12|$5|V|W|X|A|$Y|13]]|14|$5|V|W|X|A|$Y|15]]|16|$5|V|W|X|A|$Y|17]]|18|$5|V|W|X|A|$Y|19]]]]

Here are some tools not mentioned yet:

<ul>
<li>I'm using <a href="http://www.eclipse.org/tycho/" rel="noreferrer">Tycho</a>, which is a tool for using Maven to build Eclipse plugins. If you create tests inside their own plug-ins, or plug-in fragments, Tycho can run each set of tests inside its own OSGi instance, with all its required dependencies. <a href="http://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-test-plugin" rel="noreferrer">Intro</a> and <a href="http://wiki.eclipse.org/Tycho/Reference_Card#Test_bundles" rel="noreferrer">further info</a>. This is working quite well for me.</li>
<li><a href="http://felix.apache.org/site/apache-felix-ipojo-junit4osgi-tutorial.html" rel="noreferrer">jUnit4OSGI</a> looks straightforward. You make subclasses of OSGiTestCase, and you get methods like <code>getServiceReference()</code>, etc.</li>
<li><a href="http://www.pluginbuilder.org/" rel="noreferrer">Pluginbuilder</a>, a headless build system for OSGi bundles / Eclipse plug-ins, has <a href="http://www.pluginbuilder.org/documentation/run-tests/" rel="noreferrer">a test-running framework</a> called Autotestsuite. It runs the tests in the context of the OSGi environment, after the build step. But, it doesn't seem to have been maintained for several years. I think that many Eclipse projects are migrating from Pluginbuilder to Tycho.</li>
<li>Another option is to start an instance of an OSGi container within your unit test, which you run directly, as explained <a href="http://www.talios.com/osgi_based_integration_testing_with_testng_and_apache_felix.htm" rel="noreferrer">here</a>. </li>
<li>Here's someone who's written a small <a href="http://rcpquickstart.com/2008/06/12/running-unit-tests-for-rcp-and-osgi-applications/" rel="noreferrer">bundle test collector</a>, which searches for JUnit (3) tests and runs them.</li>
</ul>

blocks|key|5229017|text|在OPS4J+(ops4j.org)上有一个专门的开源OSGi测试框架，叫做Pax+Drone。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5229018|您可能想看看Pax+Drone+([http://wiki.ops4j.org/confluence/x/KABo])，它使您能够在测试中使用所有Felix版本以及Equinox和Knopflerfish。|5229019|干杯，托尼|5229020|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.ops4j.org/confluence/x/KABo]^0|12|9|0|H|15|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

There is a dedicated open source OSGi testing framework on OPS4J (ops4j.org) called Pax Drone.

You might want to have a look at Pax Drone ([<a href="http://wiki.ops4j.org/confluence/x/KABo]" rel="noreferrer">http://wiki.ops4j.org/confluence/x/KABo]</a>) which enables you to use all Felix Versions as well as Equinox and Knopflerfish in your tests.

Cheers,
Toni

blocks|key|5228928|text|Eclipse有一个启动配置类型，用于在Eclipse+(即OSGi)应用程序的上下文中运行JUnit测试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5228929|http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm|offset|length|5228930|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|35|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Eclipse has a launch configuration type for running JUnit tests in the context of an Eclipse (i.e. OSGi) application:

<a href="http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm" rel="nofollow noreferrer">http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm</a>

blocks|key|743302|text|如果你需要测试图形用户界面组件，我发现SWTBot可以完成这项工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|743303|entityMap|0|LINK|mutability|MUTABLE|url|http://swtbot.org/^0|J|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you need to test GUI components I've found <a href="http://swtbot.org/" rel="nofollow noreferrer">SWTBot</a> gets the job done.

blocks|key|3818992|text|Treaty是一个契约(测试)框架，它非常学术，但也有一些很好的想法。有关于它的论文发表，人们目前正在努力改进它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3818993|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/treaty/^0|0|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://code.google.com/p/treaty/" rel="nofollow noreferrer">Treaty</a> is a contract(testing) framework that is pretty academic but has some nice ideas. There are papers that are published on it, and the people currently working on improving it.

blocks|key|2975027|text|对于单元测试，使用EasyMock框架或创建您自己的测试所需接口的实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2975028|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For unit tests use the EasyMock framework or create your own implementations of the required interfaces for testing .

blocks|key|2975081|text|对于OSGi包，ProSyst+Test+Execution+Environment是一个有用的测试工具。它还支持将JUnit测试作为可能的测试模型之一。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2975082|entityMap|0|LINK|mutability|MUTABLE|url|http://dz.prosyst.com/pdoc/mBS_SDK/um/runtime/osgi/docs/tee/index.html^0|8|Y|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The <a href="http://dz.prosyst.com/pdoc/mBS_SDK/um/runtime/osgi/docs/tee/index.html" rel="nofollow">ProSyst Test Execution Environment</a> is a useful test tool for OSGi bundles. It also supports JUnit tests as one of the possible test models.

blocks|key|3819391|text|我认为我们遇到了同样的问题，我们制定了自己的解决方案。该解决方案有不同的部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819392|3819393|捕获所有定义了特殊属性的OSGi服务的junit4runner。它使用JUnit4引擎运行这些捕获的服务。JUnit注解应该放在服务实现的接口中。|unordered-list-item|3819394|启动OSGi框架(可以创建自定义框架作为maven依赖项)并在集成测试maven生命周期内运行单元测试的maven插件。|3819395|A+deployer捆绑包。如果将其放入您的OSGi容器中，将会打开一个简单的always-on-top窗口，您可以在其中放置您的项目文件夹(从total+commander或eclipse)。这将重新部署该捆绑包。|3819396|3819397|有了这些工具，您就可以进行TDD并让编写的测试始终在maven集成阶段中运行。建议将eclipse与m2e和maven-bundle-plugin一起使用，因为在这种情况下，只要您在源代码中保存一个类，就会重新生成目标/classes/META-INF/MANIFEST.MF，这样您就可以将项目拖放到部署程序窗口中。您开发的OSGi包不一定要有任何特殊的特性(比如eclipse插件之类的)。|3819398|整个解决方案是OpenSource。你可以在http://cookbook.everit.org上找到一个教程|offset|length|3819399|entityMap|0|LINK|mutability|MUTABLE|url|http://cookbook.everit.org/^0|0|0|0|0|0|0|0|M|Q|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$O|16|P|17|1|18]]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

I think we met the same issue and we made our own solution. There are different parts of the solution:

<ul>
<li>A junit4runner that catches all OSGi services that has a special property defined. It runs these caught services with JUnit4 engine. JUnit annotations should be placed into interfaces that the services implement.</li>
<li>A maven plugin that starts an OSGi framework (a custom framework can be created as maven dependency) and runs the unit tests inside the integration-test maven lifecycle.</li>
<li>A deployer OSGi bundle. If this is dropped into your OSGi container a simple always-on-top window will be opened where you can drop your project folders (from total commander or from eclipse). This will then redeploy that bundle. </li>
</ul>

With the tools you can do TDD and have the written tests always run inside the maven integration-phase as well. It is recommended to use eclipse with m2e and maven-bundle-plugin as in this case the target/classes/META-INF/MANIFEST.MF is regenerated as soon as you save a class in your source so you can drag the project and drop to the deployer window. The OSGi bundles you develop do not have to have any special feature (like being an eclipse plugin or something).

The whole solution is OpenSource. You can find a tutorial at <a href="http://cookbook.everit.org" rel="nofollow">http://cookbook.everit.org</a>

blocks|key|5229397|text|在过去的几年中，Tycho+-一个新的基于OSGi的Maven构建系统-在Eclipse+Foundation中变得相当流行。这个框架还包括使用Maven+Surefire在单独的测试床中测试OSGi包的方法……|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5229398|entityMap|0|LINK|mutability|MUTABLE|url|http://eclipse.org/tycho/^0|8|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

During the last couple of years <a href="http://eclipse.org/tycho/" rel="nofollow">Tycho</a> - a new Maven based build system for OSGi - has become rather popular among the Eclipse Foundation. This framework also includes method to use Maven Surefire to test OSGi bundles in separate testbeds...

blocks|key|739764|text|我想，有很多方法可以测试OSGi组件。进行测试的一种方法是使用Robot+Framework。我所做的是使用Robot+Framework进行测试，并将远程库安装在OSGi中，或者让它们通过套接字与OSGi测试组件通信，robot将与这些模块通信并通过它们运行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|739765|所以，基本上你的OSGi模块应该有一些接口来做一些事情并产生一些输出。因此，在我的设置中，我有一个测试组件，它将对实际的OSGi组件进行服务调用，然后将有一个侦听服务，它将捕获事件/服务调用(由被测模块进行)，这些结果可以由机器人询问。因此，基本上通过这种方式，您可以将一个庞大的系统拆分成小的组件，让系统在生产/生产环境中运行，并在组件级别进行自动测试，或者让一些真正的组件进行统一测试。|739766|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

There are many ways to test OSGi components, I suppose. One way of doing the testing is to use Robot Framework. What I've done is made my tests with Robot Framework and have the remote libraries either installed in OSGi or have them talk to OSGi-test components through sockets and robot would talk to these modules and run tests through them.

So, basically your OSGi-modules should have interfaces that do something and produce some output. So, in my setup I had a test components that would make service calls to the actual OSGi-component and then there would be a listening-service that would catch the events/service calls (made by the module under test) and those results could be asked by the robot. So basically this way you can split a massive system in small components and have the system run in production/production like enviroment and have it tested automatically on component level or have some of the real components be tested in unison.

blocks|key|2975365|text|与前面提到的其他插件一样，mockito在模拟插件依赖(引用等)时非常方便。请参阅https://www.baeldung.com/mockito-annotations|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2975366|entityMap|0|LINK|mutability|MUTABLE|url|https://www.baeldung.com/mockito-annotations^0|15|18|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Along with others mentioned mockito is very handy to mock plugin dependencies(references etc). see <a href="https://www.baeldung.com/mockito-annotations" rel="nofollow noreferrer">https://www.baeldung.com/mockito-annotations</a>

blocks|key|2975245|text|bnd-testing-maven-plugin怎么样？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2975246|它允许在像Felix或Equinox这样运行容器中运行JUnit。如果您使用的是eclipse的BNDTools，这一点非常相似，只是maven没有使用eclipse，没有UI。|2975247|https://github.com/bndtools/bnd/tree/master/maven/bnd-testing-maven-plugin|offset|length|2975248|另请看maven的有效also原型。这将给你一个很好的起点来构建你的项目或者只是添加测试。|2975249|https://github.com/effectiveosgi|2975250|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|22|0|0|0|0|W|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|L|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|E]]|S|$5|O|P|Q|A|$R|K]]]]

How about bnd-testing-maven-plugin?

It allow running JUnit inside a running container like Felix or Equinox.
If you used the BNDTools for eclipse this is very similar but just maven withpout eclipse and without a UI.

<a href="https://github.com/bndtools/bnd/tree/master/maven/bnd-testing-maven-plugin" rel="nofollow noreferrer">https://github.com/bndtools/bnd/tree/master/maven/bnd-testing-maven-plugin</a>

also look at the effectiveosgi archetype for maven. This will give you a good starting point to build your project or just add tests.

<a href="https://github.com/effectiveosgi" rel="nofollow noreferrer">https://github.com/effectiveosgi</a>

Currently, I am working on a new version control system as part of a final year project at University. The idea is to make it highly adaptable and pluggable.

We're using the OSGi framework (Equinox implementation) to manage our plug ins. My problem is that I can't find a simple &amp; easy to use method for testing OSGi bundles.

Currently, I have to build the bundle using Maven and then execute a test harness. I'm looking for something like the JUnit test runner for Eclipse, as it will save me a bunch of time.

Is there a quick and easy way to test OSGi bundles?

EDIT: I don't need something to test Eclipse plug ins or GUI components, just OSGi bundles.

EDIT2: Is there some framework that supports JUnit4?

OSGi Testing

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

目前，作为大学最后一年项目的一部分，我正在开发一个新的版本控制系统。我们的想法是让它具有高度的适应性和可插入性。我们使用OSGi框架(Equinox实现)来管理我们的插件。我的问题是我找不到一种简单易用的方法来测试OSGi包。目前，我必须使用Maven构建包，然后执行一个测试工具。我正在寻找类似于Eclipse的JUnit测试运行程序，因为它将为我节省大量时间。有没有一种快速简单的方法来测试OSG

问OSGi测试
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OSGi测试EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OSGi测试
EN