I have this application where users answer a survey and if there are any questions that are mandatory, the submit survey button will not be active (not clickable- grayed out) if they are not answered. Gatling is now passing the test even if the button is not clickable, is there any 'check' method that we can impose to see that the test fails if the button is not clickable? Please help. Thanks!
Gatling is not a browser but a HTTP (amongst other protocols) client, so it doesn't know anything about "clickable". You have to check based on response content.
Related
We are using the wagtailuserbar templatetag on our site and it works fine for published pages. We get the "Edit this page" and "View in admin" options etc.
The documentation says that wagtailuserbar can also be used by moderators to approve/reject drafts but I can't get this work.
Quote from the documentation:
Moderators are also given the ability to accept or reject a page being previewed as part of content moderation.
This screenshot shows the admin website with a page that has been submitted for moderation:
Clicking the preview link opens a new tab but the wagtail userbar is not visible.
If one instead uses the View Draft feature in the page explorer then again, new tab but no userbar.
Looking at the source code here these lines seem to remove the userbar for any preview view:
# Don't render if this is a preview. Since some routes can render the userbar without going through Page.serve(),
# request.is_preview might not be defined.
if getattr(request, 'is_preview', False):
return ''
My question is:
How can I use the wagtail userbar to approve or reject previews of pages submitted for moderation? The documentation suggests this is possible but experience and my understanding of the code suggests not.
It's a feature I'd really love to use.
Thanks for any help.
Thanks for this very clear description of the problem. I think this is a bug, which I've raised here:
https://github.com/wagtail/wagtail/issues/6008
I cannot delete a skill from the Skills tab.
The checkboxes to select the skill (pre-existing or added by me) are disabled.
Is it a bug or I am missing something?
Thank you
It's functionality that hasn't been added yet. We are still working on flushing out this UI. For now you will have to use the Swagger UI to do this. Click on the Conversation API link from the Console page and use the DELETE /v2/api/skills/{skillName}
Remove a skill API.
I have incorporated Google ReCaptcha in my angular project on the client side and it was working fine. I have not changed anything but now I am unable to get image validation dialog box like I used to get before.
Now when I check on "I am not a robot" It verifies directly without asking for image validation and I am able to get the response string from Google API.
Is this behaviour is expected? and what can I do if I want Image validation after checking on "I am not a robot"?
I figured it out when I tried in another browser it asked me for image validation because after testing many times and verifying by my server, recaptcha does not ask for image validation.
Is it possible to customize or override the salesforce logout method in apex? I want to do some thing custom when user goes to logout salesforce account.
enter image description here
You screenshot shows the standard logout link which can not be customized.
You can customize the "logout" flow in a community using custom code by having a custom logout link which calls a controller action which wraps the standard logout function but this is only in a case where you are not using the standard header and can implement a custom link for logging out.
The logout flow of salesforce is a standard anchor tag call with a href to a link. If you inspect the element you can see that.
Logout
Unfortunately, there is no controller where the control comes after a click of the LogOut option. The only way you can get some control is, if you customize your logout URL and make salesforce redirect to it after it logs itself out. In that way, you can solve the branding issues but can not do anything related to the user as the user context is lost as soon as salesforce logs out itself.
Though in the idea forum there are ideas for doing that but looks like Salesforce is not doing anything in that front.
Hope this helps.
Is there a way to make the value in #Stories annotation to be a hyperlink? So that user can click on it and open a page.
The value in the #Story now cannot be used as link.
Now you just can provide property for testcase and it can be link. We have an example of this approach on our teamcity (click "login as guest" to get in). There you can see the url of the tested page above the steps block. It is clickable and leads to tested page.
If these way is not suitable for you, please report an issue and give more infromation about your use-cases of this feature