I have a project using Nuxt for front-end and firebase for back-end. I had written unit test for it by using Jest. But when write E2E test using Cypress, I can not find the way to mock data when calling firebase-function:
firebaseFunctions.httpsCallable(functionName)
I find a package is cypress-firebase but it doesn't include firebase-function.
Please help me how to write E2E test for system using fireabse as server-side or best way to E2E testing such as test with staging URL. Thank you so much.
Related
I'm trying to write some Unit and Integration testing using XCtest.
I have a part that I'm not sure if it is a unit test or Integration test :
I need to test uploading one document using an upload service .
My question : Since my function is going to interact with a different service "upload service" so I'm thinking that it is an Integration test more than a unit test.
Could anyone please confirm ?
My organization is looking to implement CI/CD in our deployment process and I've been tasked to setup the test automation part in the pipeline. I did a lot of reading and I've got an idea on how the setup should look like. Can help to go through my idea and advice if it's indeed the correct setup and give some ideas on improvements if needed?
Here's how I have pictured the setup in my mind. My organization have 3 environments, Development, Testing and Production. Test automation scripts in the pipeline will be executed in the Testing environment.
Dev to check in the code in the Development environment.
This will then trigger the deployment to Testing environment
Once the deployment is complete, it will then trigger the test automation scripts in the repo via the test suites id
Each pipeline will point to specific test suite id
The automation scripts will be used to perform regression testing to ensure the new changes doesn't break existing functionalities.
At the same time, testers will be doing manual testing in the test environment to ensure the new changes works as it's intended.
If both the test automation scripts and the manual testing passes, we can then proceed to the next stage. (UAT Approval and then PROD deployment)
Would this be the correct process flow?
Many thanks in advance!
Im currently working on a project were i'm importing the output.xml from my test suite to JIRA via XRAY. This create the test (in case they don't exists already) and the execution test (with the results).
My problem is that right now, the test are created without description or documentation. Is there a way were I can set the [Documentation] field from the test cases in robot to the JIRA issue (test) via XRAY? I don't find anything in the XRAY API doc.
Maybe my only option is parse all the [Documentation] field of the tests cases and then import in the test on JIRA without XRAY?
Currently this is not yet possible but it make sense in my perspective.
You can vote and follow this suggestion so the Xray can be aware about your interest on it.
You can implement your own script to go over the Tests and update the Description field (using Jira's REST API) but you would need to know their key in advance; if that's the case, then fine.
One of our customers uses Katalon Studio and would like to see the reporting results in Xray and Jira again after the execution of the test cases.
Do I have to create a Json file at the end of the test run? That I have to import into Xray?
Is the Katalon export plugin sufficient here?
Or does the Xray plugin offer me exactly this way?
as of today, AFAIK, Katalon doesn't have yet a specific integration with Xray. You may ask the Katalon team to provide it by submiting them a feature request.
Meanwhile, you can follow these intructions to have visibility of the results in Xray using a JUnit XML report which will autoprovision Test issues.
https://confluence.xpand-it.com/display/XRAY/Testing+APIs+using+Katalon+Studio
If you would like to enforce a specific test in Katalon to an existing Test issue, you would have to use a different format such as Xray JSON; however, that would require you to build it using some logic based on the information in Katalon.
I currently have firebase setup and working on my device, I make sure of the storage and real time database and they both work great!
I thought I'd give the robo test a go to see what it does as it mentioned I would not need to add anymore code. Although when attempting to run the robo test with just the default 1 device ( Nexus 5g 23 ) I get the following error:
Normally I would assume I need to go into firebase within Android Studio and setup the gradle to enable this type of testing but the only option I have is the following.
which leads me to the more standard type of testing. I do not believe this is necessary for the Robo lab testing from my understanding (although I may be incorrect).
What's going on how can I use the Robo test? Thanks
This message is probably refering to the APIs enabled for the Firebase project being used to run the tests.
The project selector is shown in the upper-left corner of the Firebase web console (console.firebase.google.com). All of the required APIs are supposed to be enabled when a Firebase project is first created, or when a Google Cloud project is imported into Firebase. It is possible that one of the APIs was disabled or that this process didn't succeed.
Visit https://console.developers.google.com/apis/dashboard?project=your-project-id and take a look at which APIs are enabled. Test Lab uses the "Google Cloud Testing API".
Here is the list of APIs that are enabled for one of the projects that I use for Test Lab.