I was writing a test in Karate in VS Code, at some point I made a mistake and afterwards reverted it but when I was running the 'mvn test' command it was still running the wrong version of the code. I decided to delete the feature alltogether but it is still being tested and shown in test results even though the file no longer exists. Is this some issue with cache? If so, anybody knows how can I solve it?
Thank you!
Have you tried deleting the contents of your target folder or try a "clean"
karate -C
Related
When I run tests in test explorer individually they all run without errors.
When I click on "Run All" I get varying test that fail.
My question:
Does anybody know what the minimum requirements regarding tests to be able to run them with "Run All"? Like maybe they all have to in a certain way with a certain command?
Running test manually one by one or run all has nothing to do with your tests being failed. You need to check the failure reason for each test and solve it.
Maybe you can post the error messages here so we can help you better.
I discovered that I had a static variable still containing a value other than that expected. Now the outcome is always the same regardless of how I run it.
Sorry for troubling you all
We do have troubles getting our CI to work with Xcode. We encounter the issue Could not determine bundle identifier for xxxTest TEST_HOST: some path that does not exist.
What we have done so far:
On the CI Machine we are able to run all tests on the device, but if we trigger it with a commit the CI does end in that error.
We had that issue on other machines too, when we tried to run the tests of the application. We fixed that by cleaning the machine and reboot the devices.(Had do fix some scheme settings) Not we can run all tests but we run into the issue sometimes without any reason.
We also double checked the schemes. The Host Application is set in every Tests scheme to the App itself.
Our project has the following targets:
App
App Unit Tests
App UI Tests
AppeareanceKit (Module)
AppeareanceKit Unit Tests
Models (Module)
Models Unit Test
Found solution:
Diabling the Tests except the App UITest
Run the tests once
Enable all Tests
Run the tests
Question:
What is happening there? How can we prevent from having that issue over and over again?
Known questions:
Xcode 8 Beta - Convert to Current Swift Syntax Failed: Could not find test host
Tests stop working under xcode 8 TEST_HOST error
So after ages of having this issue, we could find the right checkbox to fix this issue.
It somehow sounds weird but the issue was the configurations for the command-line builds inside of the Project settings.
I assume this happens because we always test against the debug configuration and it was set to release. Therefore it did the wrong build for the test host.
This does set the defaultConfigurationName inside of the {projectname}.xcodeproject.
Please comment if you have any more insights of this.
In my app I found a solution.
The problem was of course in the test target.
I hope that this solution will work for you too. Go to your test target build settings.
Search for test host.
In my case this testHost was looking like
build/{buildConfigurationName}-iphoneos/{schemeName}.app/{appName}
Which is wrong as the actual path must be
build/{buildConfigurationName}-iphoneos/{schemeName}.app/{schemeName}
so if you have a build configuration called Alpha, in your app named MyApp, with a scheme called MyApp-Alpha the test host path should be
build/Alpha-iphoneos/MyApp-Alpha.app/MyApp-Alpha
it was
build/Alpha-iphoneos/MyApp-Alpha.app/MyApp
I hope this can help... unfortunately this issue appears in many cases.
One reason to have this error is that your info.plist of your target is not in its path. So if you moved it or removed the reference to it, you may get this error.
So if you moved it, put it back into its place or path. if you removed the reference to it, add it again, close and reopen the project.
I'm using an InstallShield project to generate setup files. Everything was working fine, but I've recently encountered following error which says,
Could not compress "bin\x86\QA\AppManifest.xaml" into "\Default
Configuration\MSI
Could not find file
"bin\x86\QA\AppManifest.xaml" ISDEV : error : -6103:
So far I have been unable to fix these issues. Can someone help me understand what I may be doing wrong?
Thought it's late to reply, I came with similar error on dynamic file linking. But, problem was with double slash being on Resource directory.
My problem was, I provided path as : "PATH_TO_HELP_FILES\Docs\", while i removed the last \ on path i.e PATH_TO_HELP_FILES\Docs, the problem was gone.
It could be the AppManifest.xaml is missing from the source folder? I think this is the most likely scenario - your application build could have failed, and this particular file could be missing?
You could also have a file lock in the build output folder - did you try to reboot and rebuild?
You can also try to run the release wizard and make a new release configuration and try to build that
http://www.codeproject.com/Articles/192738/What-is-AppManifest-xaml-in-Silverlight
Another late reply. For my situation, I merged multiple branches together, and something is lost along the way. It was probably a setting file or something with the gitignore file. Anyways, I got that same -1501 could not compress file error. The reason was the build order of projects in the solution. Incorrect build order caused VS to look for dependencies when they were not yet created or included. I right-clicked on the solution, went to the Dependencies tab to set the order (by setting dependencies). Once that was done, I could Clean Solution and Rebuild Solution without getting any error.
we are facing strange scenario while using jenkins. We have created and scheduled jobs in jenkins and assigned few nodes(Windows Machines) to it and executed! After a week all our jobs got deleted automatically. Is this an expected behaviour of jenkins and do we have a solution for it?. Thanks in advance.
That's not an expected behavior. Try to find out what happened and try to reproduce it. If you can reproduce it, then someone might be able to help you with your issue (if it is still an issue then).
I have recently attempted to upgrade a solution from VS2010 to VS2012, and as part of that I have introduced the new .runsettings file to generate code coverage results.
In order to specify the run settings file I have had to un-select the .testsettings file that was working in VS2010. As soon as I do this and run my tests, a large number of them start to fail because the CollectionViewSource.GetDefaultView method returns null instead of the expected default view.
If I re-select the old .testsettings file then my tests all pass, but the code coverage settings are incorrect.
Has anyone else experienced similar problems with the upgrade?
I worked out what the problem was: one of the unit tests was manually restarting the Dispatcher as part of some cleanup, and that worked fine in VS2010 but not in VS2012.
I guess this is pretty specific to the one solution, but it might provide a clue to anyone that finds this.