I am getting "ClassDefFoundError:org/eclipse/e4/core/di/InjectionException" error while writing Junit test cases for one class.Please note that while debuging it is pointing to Dispay display=platformui.getWorkbench.getDisplay() for my original class. Can anyone please help how to handle this dependency?
Related
I have a VcsFullCommitDetails, calling .getChanges() is returning empty array all the time. Appreciate any help or hint how I can resolve that.
Take a look at methods in git4idea.history.GitHistoryUtils
See https://intellij-support.jetbrains.com/hc/en-us/community/posts/360001208300-Get-a-list-of-commits-in-project
I'm trying to perform a Where Used Query for a method of a class. It doesn't work. First, the query runs for minutes. Then finally it responds with an error that Where-used is not supported "for this object", which doesn't make sense for a class method. Has anybody seen this before? Your help fixing this issue will be appreciated! FYI, I'm using Eclipse Oxygen with latest ADT installed.
Error Message
I am an automation + manual tester. I would like to understand the reason how understanding the logs of an application(which i am working on) help me in improving my testing skills.
By viewing logs you will get some ideas about the error, if it is data level fix you can release and fix directly without dev team help.
In Java some times Runtime exception will occur, it will not convey messages to you in the interface about the exact problem. By viewing log you can get some ideas about the Runtime exception.
You see, I am really new into android, but the reason logs are important is because they can help you track down issues, such as Java.NullPointerExceptions and can help you trace back to where the issues were. I think there is also a way to create an error dialogue in the log, which can tell you that an error occurred. This is particularly essential in debugging, where you need to solve a problem in your app. I hope this helps, and best of luck. I think you can search up how to write stuff into a log at certain areas. I think the way on how to Log is to access Log class. http://developer.android.com/reference/android/util/Log.html
Can any one please tell me is there any kind of tools or eclipse base plugins available for generate relevant test cases for SalesForce platform related Apex classes. It seems with code coverage they are not expecting out come like we expect with JUnit, they want to cover whether, test cases are going through the flows of the source classes (like code go through).
Please don't get this post in wrong, I don't want anyone is going to write test cases for my codes :). I have post this question due to nature of SalesForce expecting that code coverage should be. Thanks.
Although Salesforce requires a certain percentage of code coverage for your test cases, you really need to be writing cases that check the results to ensure that the code behaves as designed.
So, even if there was a tool that could generate code to get 100% coverage of your test class, it wouldn't be able to test the results of those method calls, leaving you with a false sense of having "tested code".
I've found that breaking up long methods into separate, sometimes static, methods makes it easier to do unit testing. You can test each individual method, and not worry so much about tweaking parameters to a single method so that it covers all execution paths.
it's now possible to generate test classes automatically for your class/trigger/batch. You can install "Test Class Generator" app from AppExchange and see it working.
This would really help you generating test class and saves lot of your development time.
what are difference between a bug and script issue?
and when ever a testcase is failed, how to solve that testcase, i mean what are basic
points to check how the testcase is failed.
The term "test case" is to generic - what do you mean by it in your context?
However generally in the test case you should identify the condition(s) that will make this test "passed". So if condition(s) is not satisfied the test is failed.
Generally the issue is some problem with something (for example, problem with the script). It may be the system configuration issue that prevents the script from successful execution or it may be an error in the script code, and this will be a bug in the script.