I am using allure behave module.
i have my results in allure-results.
To make it even more convenient i have made sub directories in it. Each sub directory will have logs for each json.
from the below question i came to know that allure doesn't support subdirectories,
Allure-report empty when allure-results have multiple result folders
What if i change the source of log in json file with sub directory name??
source before: source:"XXXXX.txt"
source after in json: source:"/subdir_name/XXXXX.txt"
i tried it it didn't work. Wanted to know if i can upload logs from that specific folder to allure report.
TIA
Related
I have two webapps - "manager" and "viewer" - coded in separate VSCode projects. These are deployed to a common Firebase project where they share a common database. The "manager" webapp is used to maintain the database and the "viewer" provides public read-only access.
To create the "page" structure I have added a robocopy to React's build script for each VSCode project to produce a structured "mybuild" folder with the page subfolder within it. Firebase.json's "public": setting is then used to deploy from "mybuild".
Individually the two pages work fine, but each deployment overrides the functionality of the other. So, following the deployment of "manager", webapp/viewer returns a 404 (not found) error and vice versa.
To cut a long story short, the only way I've found around this is to manually copy the results of a deployment for one project into the "mybuild" folder of the other and then deploy from this. But this is no way to proceed.
I think I've taken a wrong turn somewhere here. Can anyone suggest the correct "firebase solution" for this requirement? In the longer term I'd like the viewer webapp to be available at the root of some user-friendly "appurl" while the manager is accessed via "appurl/manager", but other arrangements would be acceptable. The main issue right now is finding a simple way of maintaining the arrangement.
I needed to fix this fast, so here's my own answer to my question.
It seems that when you deploy a project, firebase replaces the current public folder for your URL with the content of whatever folder is specified in your firebase.json. So I decided that I had to accept that whenever either of my projects was deployed it must deploy from a "composite" folder that contains the build files for the other project as well as its own build.
That being the case, it seemed I was on the right lines with my "manual copy" approach and that what I now needed to do was simply to automate the arrangement.
Each of my projects now contains a script file with the following pattern:
npm run build
ROBOCOPY build ./composite/x /E
ROBOCOPY ../y/build ./composite/y /E
firebase deploy --only hosting
In each script, x is the owner project and y is the other. Additionally, firebase.json in each project is edited to deploy from composite.
When I run the script for a project it first builds a composite folder combining the latest build state for both that project and its partner, and then deploys the pair.
The final twist is to tell the react build process that the result is to be deployed from a relative folder and so that the build therefore also needs to use relative references. I do this by adding a
"homepage": "https://mywebapp/x",
to the package.json for each project. Here, x is the name of the project.
I'm not able to convince myself that there's not something wrong with my whole approach to this issue, but at least I have a fix for the immediate problem.
I have a project to test UI on Java Selenide. I want to show it to one company as a portfolio. I do not want them to bother installing allure command-line tools and add its bin to the PATH variable. Is it possible to generate an allure report without it?
I am talking about the Windows environment.
Assuming you have Allure specified in your pom (and you're using Maven), after your test run you can run this:
mvn allure:report
This will generate a report in the target/site folder (click on index.html to view it)
I'm using the jenkins test-results-analyzer plugin, which uses the jenkins Junit plugin. They get the test results from the jenkins archive and import them into the plugins. I then delete the archived test results, and the test results are still visible through the test-results-analyzer plugin. This suggests that the test-results-analyzer/junit plugins must be storing the test results somewhere....but where?
I've run "du -h" in the jenkins script console and have looked at the directories containing both plugins but nothing jumps out as storing the test results, either in terms of naming convention or directory size...
I am trying to live debug a Python Google App Engine Standard application in Stackdriver Debug console. When I click on a deployed file (main.py) and the line where I want it to break, I get an error message stating "Multiple modules matching" and lists a couple files with the same name.
This is a new deployed version with that filename being unique in my project. I wouldn't expect it to see multiples of the same filename. Because of that error, I am unable to debug the deployed app.
The debugger loops through all the loaded Python modules in the project and may find a file with the same name. When multiple files are listed, copy and paste the full path to the file you are wanting to debug.
Example: apps/[PROJECT]/[VERSION.UNIQUE_ID]/myfile.py:[LINE_NUMBER]
You can copy the full path from the file listed in the error message.
I was creating .exe file via install sheild for my wpf application but at a point where we need to put the project output files I got confused.I want to add xml files considering the fact that it should point to local reference application bin/ debug folder.
How to achieve this? Any help would be appreciated.A walkthrough would be of great use.