We run our Cypress tests locally (in Jenkins) and create Mocha test reports (JSON).
Now we would like to send these reports to Cypress dashboard so they are more easily accessible.
We have looked in to ReportPortal, where you can include the dashboard server information in the reporter configuration.
Is there such configuration for Cypress dashboard where we can send the reporter results to the dashboard?
Thank you.
I don't know if I understood you exactly. In my experience to upload reports to cypress dashboard you have to:
configure a project on cypress dashboard, and there you get a "project id" and a "record key"
then you have to configure the project id in the cypress.json
{
"projectId": "<your project id>"
}
finally you have to call cypress with record key:
cypress run --record --key <your record key>
Related
My secret value is stored in Azure Key Vault.I have given access to key vault and load test resource. I need to send this secret in Azure Load Test yml file and run azure load tests in pipeline. When I run pipeline, it says invalid secrets. Please help how to pass this in yml file to run the test.
This is how I parameterized the HTTP request
enter image description here
I used getSecret function in retrieve the value
enter image description here
This is how I passed them in load test yml file:
secrets: |
[
{
"name": "secretValue",
"value": https://secret.vault.azure.net/secrets/Mysecret/45ff4094dsk9gkjdlkja5134a035uj0
}
]
I don't know what is "Azure release pipeline" and I don't know what is __GetSecret() function, if your test works locally and doesn't work in the "Azure release pipeline" it means that you need to install the JMeter Plugin which provides this function somehow.
If you're installing JMeter from scratch - make sure to put the .jar(s) implementing this __GetSecret() function on JMeter Classpath
If you're uploading your script to some form of a cloud load testing solution - it might be the case you can provide the .jar file with this __GetSecret() function along with your script
Using the Thirdweb SDK: NFT Gated Website, I created a local cloned project using the following command:
npx thirdweb create --template nft-gated-website
Updated the const/yourDetails.js and created .env.local as instructed. Then, I launch the local development server via:
npm run dev
Login is successful via MetaMask with Mumbai Testnet. However, when I try to claim the testing NFT, the following error occurred:
{"code": -32603, "data": {"code": -32000, "message": "transaction underpriced"}}
and the Transaction failed. Sometimes the transaction is successful (after few attempts), one of the transaction records can be viewed here; everything looks fine, but the template script cannot detect that I owned the test NFT.
What could be the reason behind this?
I run my tests in the docker container and I would not want to see the logs about the results of the tests (since I run several instances of cypress and logs are mixed). Is there any way to turn off logging?
I have read documentation but i haven't found anything.
As per this github issue: https://github.com/cypress-io/cypress/issues/2071.
That issue was resolved at the 4.9.0 release of Cypress.
You can now run your Cypress tests with the --quiet flag. e g.:
cypress run --quiet
my requirement is to run postman scripts in bamboo. We have a repository for the collection.json, however, as my environment file has some sensitive data like client_id, secret_id, username, password etc I can't push it to my repo.
Please advise me how can I run my collections in bamboo using Newman.
You can utilize your environmental variables if you have a Postman account:
You'll need to get the X-Api-Key for your Postman project (on your Postman account), then you'll be able to use Postman API calls to get the collection and environment ids. Here's the link with Postman API documentation.
Install Newman to your npm. Here are the details about Newman
Run a command line from your bamboo that will trigger the Postman test run.
The command will look this way:
newman run https://api.getpostman.com/collections/{{collectionId}}?apikey={{ApiKey}}
-e https://api.getpostman.com/environments/{{EnvironmentId}}?apikey={{ApiKey}}
How do you push an UI Test along with the associated app to App Center Test from the command line?
I'm using a CI (Continuous Integration) server to build my app, and I tried using the following command, given by the App Center Test portal, but it isn't working and outputs the error, below:
appcenter test run uitest --app "bminnick/uitestsampleapp" --devices b139e40f --app-path [my apk file path] --test-series "master" --locale "en_US" --build-dir [my UI Test Build Directory]
Command 'appcenter test run uitest' requires a logged in user. Use the 'appcenter login' command to log in
I'm trying to deploy a Xamarin.Android app and a Xamarin.UITest.
Push to App Center Test from CLI
1. Manually Retrieve an API Token
The App Center CLI requires the user to be logged in, and we can log in from our build server by providing a login token.
Using the App Center CLI, enter the following command, replacing [Name Of Token] with whatever you want to name this token
appcenter login
appcenter tokens create -d "[Name Of Token]"
It will provide a response like this:
ID: [Unique Guid]
API Token: [Unique API Token]
Description: [Name of Token]
Created at: [Time Stamp]
Copy the API Token result. We will use this in our CI script.
2. App Center Test Script for CI Server
In your Continuous Integration pipeline, use this bash script to push the APK File + UI Test to App Center Test
The bash script does the following:
Locate the UI Test Build Directory
Replace [My UI Test Assembly Name] with the name of your UI Test assembly
Locate the APK file
Install the appcenter cli
Log in to App Center using the API Token
Push the APK + UI Test to App Center Test
#!/usr/bin/env bash
UITestDLL=`find . -name "[My UI Test Assembly Name].dll" | grep bin`
UITestBuildDir=`dirname $UITestDLL`
APKFile=`find . -name *.apk | head -1`
npm install -g appcenter-cli#1.2.2
appcenter login --token [login token from Step 1]
appcenter test run uitest --app "bminnick/uitestsampleapp" --devices b139e40f --app-path $APKFile --test-series "master" --locale "en_US" --build-dir $UITestBuildDir --async