As an admin user, I find myself unable to delete any test cases currently located under the test specifications. Every attempt to delete a test case results in the following message:
Your role has no right to delete executed test cases or test case versions
It appears that you can create a new role from the "user/roles tab" with rights to do this, however the settings do not persist on my installation. Not sure if this is just my installation or a generic issue. I intend to investigate this week and will update.
Related
I'm using a free Microsoft Account (#outlook.com) on VSTS. I created my first proyect, configure it and make it works with CI/CD. Now, I'm creating a new proyect and I want to add a build definition, but I don't know why, all the options appears disabled.
No matter what I do, the Save button remains disabled.
¿There is a limited number of projects to use with CI/CD per account?
Thank's in advance
This is a very strange behavior, but finally I found the solution: in the querystring params you need to remove the "path" parameter (path=%5C)
Reference: https://developercommunity.visualstudio.com/content/problem/203956/build-definition-buttons-are-greyed-out.html
When setting up a basic A/B test on a component using page editor, I received error with the following appearing in the log:
Exception: System.InvalidOperationException
Message: Test item is not in workflow
Source: Sitecore.Analytics
at Sitecore.Analytics.Data.Items.TestDefinitionItem.Start()
at Sitecore.Shell.Applications.WebEdit.Commands.Testing.StartTest.Run(ClientPipelineArgs args)
Attempting to start test created a Multivariate Test Definition Item with empty workflow section in the Test Lab
I'm thinking that those Workflow fields should have been appropriately set when using the UI on the page editor to create and start the test.
I guess I'll try reflector to find that error message in the binaries and keep digging.
Sitecore Version: 6.5.0 (rev. 120706)
I realize this is an old question, but I just encountered the same thing in 8.1 update 3. In my case it was because the workflow associated with testing (Analytics Testing Workflow, unless you've made your own) had been deleted on my local installation. Restoring it from one of our other servers made the error go away.
In Sitecore 8.1 and above there is a setting which can be turned on to allow the content authors to start test via experience editor.
Please add the below settings either as patch config file or
You can edit the value in the config file (Sitecore.ContentTesting.config).
Setting name is “ContentTesting.AlwaysShowTestCandidateNotification”
I am working on a testing automation project and I am able to automate end to end test cases but in my scope I have to enable functionality to run test-case when a workflow is checked-in to repository. For this I need a trigger with information like what workflow and in which folder is checked it's checked in. Unfortunately I am unable to get anything till now and my admins are also not sure if this can be achieved. Any lead will be a great help.
Even if I can get the logs of workflow check-in, I can process them in real-time to get this information.
I have developed module with sql script upgrade and after that my phpunit tests got not success, these break in place of call new attribute for customer.
I have investigated this case and concluded that new updates has applied after manual clean cache on the administrator page but don't after console command like zf clear mage-core-cache and etc. I think that runs anything else except cleaning cache...
Anybody know how to run check upgrade scripts like mysql4-upgrade-1.0.0-1.0.1.php and apply these programmatically ? I need that for my phpunit tests. thx
From memory its Mage_Core_Model_Resource_Setup::applyAllUpdates(), but that relies on Mage_Core_Model_Config being initialized at least. It works through Mage::run() workflow.
i try to install my WebService on Windows-XP,
and i got this error:
The installation of
C:\MyWS\MyWS_Setup.msi
is not permitted due to an error in software restriction policy processing.
The object cannot be trusted
what can be the problem ?
thanks in advance
Run regedit and verify that there are no policy restrictions disabling installer under this key:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
If there are, just right click on them and delete them. A reboot may be necessary.
The restriction name would be "DisableMsi"
Also, as a test, if you are logging in as Administrator in Safe Mode -- could you try creating a new User Account and giving it Administrative rights and test these issues under the new account in normal mode?
One more thing, just to make sure the account you are having problems with in "normal" mode really has administrative rights, would you right click on the Start tab and see if "open" and "explore" "All Users" is present?