When editing deepviews on branch.io I want to test them first on my staging site and only then use them on production. I tried everything, but every time I change something on test it also changes on live.
Is this working at all or am I doing something wrong?
Brian from Branch here. When you create a template on the Branch TEST dashboard, a new template with the same name/key will also appear on the Branch LIVE dashboard. However, they are independent from each other and editing the template on the TEST dashboard will not affect the templates on your LIVE dashboard.
Please ensure that you are initializing your staging site with the Branch TEST key to ensure that you are retrieving the correct template design.
LIVE dashboard:
TEST dashboard:
Related
How do I get the below options like test details (to add BDD scenario) when creating test cases?
enter image description here
On my one it just looks like this. I have imported the 6 test type from Xray into my JIRA project. Is there more configuration that needs to be done? Once created, I can click on the test case and insert the scenario there, but surely I should be able to do this whilst creating in the first place. I can't find anything on this new layout online.
enter image description here
If you are using Xray on Jira server/Data Center, then you can fill out the Cucumber Scenario details right away as mentioned here.
If you're using Jira Cloud then you can't do this due to current limitations on Jira/Atlassian side; in this case, you have to create the Test first and then edit the scenario/scenario outline from the Test issue screen.
On the dashboard, I have two domains: “Default Link Domain” and “Alternative Link Domain”, but when I create a new link using the API, I get a link without this domain, something like this “app.test-app ". It’s very important for me that my link is without a “test”. And also I don’t understand how it works, how this domain appears in my link. Could you please explain it to me?
Here is my branch.json
{
"debugMode": false,
"liveKey": "key_live_****",
"testKey": "key_test_****",
"useTestInstance": false,
"delayInitToCheckForSearchAds": true,
"appleSearchAdsDebugMode": true
}
When I set up my application, I added a test key to info.plist and forgot about it. After I changed it to a live key, everything worked perfectly!
A Branchster here -
By default your Branch app has two modes - Live and Test. When you are using the API to generate a new link make sure you are passing in your Live API key. If you use your Test Mode API key then you'll get corresponding test link like "yourapp-app.app.link/xxxx"
You can read more about it here - https://help.branch.io/using-branch/docs/advanced-settings-configuration
I've recently started to use Selenium IDE for the automatic testing of a website I'm working on. I've created all the test cases with the LIVE base URL. Then I created a test suite but now I would like to apply all the tests to the staging environment.
I tried two things:
Update the base URL from the test suite. I opened the test suite, when to each case and changed the base URL in the field at the top. Saved and closed.
Update the base URL in each test case, individually. Yep, I opened each test case (amd there are like 60 or something) and changed the base URL both in the top field and in the source (in the link rel tag). Saved and closed.
My problem is that none of these changes have been saved, I've applied them 3 days ago and now I've opened the test suite or the test cases, they still have the LIVE base URL.
I'd be very grateful if someone could help me figure out what I did wrong or if I'm obliged to start again from zero.
Best regards
Samkoukai
Try opening each test case in an HTML editor (like Notepad++, or even just Windows Notepad) and edit this link to the base URL you want:
<link rel="selenium.base" href="http://www.yourwebsite.com/" />
I am helping a client redesign their website through Hubspot. Their existing site is within Hubspot and their new website will also be within Hubspot. I am attempting to run the development through Hubspot's Content Staging as per this link: https://knowledge.hubspot.com/website-user-guide/how-to-redesign-and-relaunch-your-site-with-content-staging
The problem is that this appears to be on a per page basis rather than a per site basis. A problem with this is that I am unable to stage files such as the primary CSS file, or other CSS/JS files that I need to make changes to, but that the existing website will need to keep untouched throughout development.
Does anyone have any experience redesigning a Hubspot website who may have some advise for me? What am I missing?
Thanks!
When I'm redeveloping a HubSpot site within a client's portal, i'll do it on a template by template basis.
So for example, if you're making a new home page, just attach any stylesheets and scripts you need in the template file itself - found in the Edit > Edit Head menu. Here you can disable the Primary CSS file, and you can also disable domain specific stylesheets (the ones you add in Content > Content Settings) so that your template is only using the assets you want it to use.
Using this technique, you can work on individual templates, and then stage any pages that are using said templates independently of the rest of the website. Finally when you're ready to make your changes site wide, merely move your assets from the Edit head area within your template to the Content Settings area.
I am developing an analytics product similar to Google Analytics and want to offer an integration for our Shopify users.
I would need to do just two things:
1) Insert our JavaScript snippet into the body of all the shop's pages
2) Insert a second conversion snippet into the body of only the "thank you" page after a purchase to record the sale, passing back the order total and order number
Could you point me in the right direction?
The ScriptTag endpoint looks optimal except that it doesn't seem to provide any way to differentiate between the "thank you" page and other pages, or to pass the order details from the "thank you" page into the script.
It seems like I either need an endpoint that can inject arbitrary code into all pages, or one which lets me alter the theme layout file to add code before the </body> tag.
If I can do that much, it looks like I might be able to use a conditional in the templating language to only show the conversion code if the URL matches the "thank you" page URL, and use {{ total_price }} and {{ order_number }} in that code.
Does the uninstall webhook allow me to make changes before the rights for the app are revoked? It seems like I would need a way to clean up at uninstall to remove my code from the theme, if I'm allowed to edit the layout file.
itThere are two ways you can go about this:
ScriptTags: You're already aware of this method. It's true that the script is loaded into each and every page, but you can look at document.url in your js to figure out which page you're on and conditionally execute code based on that.
Scripts inserted this way are executed during the 'onLoad' event. At that time you have access to the DOM and can do basically whatever you want with the page.
Snippets: Using the Assets endpoint you can make arbitrary changes to the user's theme. Be careful with this power! The recommended way to make complex changes to a page is to create a custom snippet in the theme with your additions and then tell the user to insert an include tag into their code where it needs to appear. This reduces clutter in the main theme files.
I'd recommend using ScriptTags wherever possible. As mentioned below, they don't need cleaning up and remove the need for user interaction when setting up the app.
--
As for the uninstall webhook: It is fired after the app has been uninstalled from the shop, so you no longer have access. It's designed to be used to trigger cleanup on your end (remove db entries, etc.). Note that ScriptTags and Webhook subscriptions are automatically cleaned up, but any changes you've made to the theme aren't
You ask a lot of questions in one posting.
For your #1 and #2 read:
http://api.shopify.com/scripttag.html
Secondly, for your app install/uninstall read:
http://api.shopify.com/webhook.html
Pay attention to the part about app/uninstalled since you're interested in that.
As for knowing when someone installs your App, that is really up to you to figure out. Should not be too hard since you probably read about how to make and App in the first place. Shopify provides lots of boiler plate code on github that can show you almost everything you asked here.