test-output | Test : :Output - Utilities to test STDOUT and STDERR messages | Unit Testing library

I am creating a cucumber project with extent reporting. I have used the cucumber extent adapter 5 plugin. All is working fine while I use extent.properties file for configuration. But when I set the system properties as shown below (instead of properties file)

I have an issue where the screenshots that i take dont show in the TestNg Report Plugin i am pretty sure that the probleme is the path i am giving them but i dont know what other path i can give is there a solution ?

My screenshot taking code :

I am trying to store JSON data that has been dumped into an input S3 bucket and convert the file into CSV in another S3 output bucket location using Athena's Start Query Execution.

1. I am using a large Query that would be inserted into a temp table (using INSERT INTO).

2. That table is partitioned into year, month, day and hour.

3. Using AWS Glue I was able to set up storage.location.template for the query table (See screen scrape)

   s3://prod-cog-kahala-test-output/data/landing/olo/baja/year=${year}/month=${month}/day=${day}/hour=${hour}

4. I am also using projection year, hour, month, and day using AWS Gue on this table. (See screen scrape)

This output patch is dynamically created based on the date and time when the event has fired. It will store CSV files from JSON that were created during that event time the Athena's query. The output path should look like the following screen scrape:

I am using python lambda to extract the event record's eventDate value and then using an Athena query, output the csv files to the dynamic output path

Note: I have only been able to run this successfully using a static S3 path but not a dynamic S3 path which is a requirement .

When I ingest/extract an input JSON file in the input S3 bucklet, I get the following error when Athena runs the query using dynamic S3 path:

After checking my permissions, roles, and policies I would suspect that I have the permissions to write to the Athena output locations in S3 but for some reason whenever a file lands on an input S3 bucket to trigger the Athena query to run a large query within my Lambda python integration, I notice that:

• I don't get any type of HTTP return code from Athena in AWS Cloud Watch although the code runs without errors.
• I don't get any CSV files located in the Athena S3 output bucket.
• When I test the query inside of the Athena console, it displays the correct output.

I am not sure why. I did do an Alter Table in Athena to make sure that the tables point to the correct output location too. Here are the following screen scrapes of the code, permissions, and policies: (Note that in the last two screen scrapes the client_name variable cotains one of 2 different tables that Athena will use as a query. The variable athena_output_bucket is a global variable which has been previously set as default (i.e. athena_output_bucket = "s3://prod-cog-kahala-test-output/baja/"). Thus it toggels based on the name of the input file that was dropped on S3 input bucket. Thanks much for all the help. Policies

I want to store all new and previous reports in my directory.

Current behavior

Right now after running tests by 'npm run test' previous reports are deleted or appended (when i delete line clean reports in package.json).

Desired behavior

I want to give my directory path a dynamic name e.g with current date or number so previous ones stays where they are but i don't know if it is possible to do it inside cypres.json. Is there any solution workaround?

Code

package.json

"scripts": { "clean:reports": rmdir /S /Q cypress\reports && mkdir cypress\reports && mkdircypress\reports\mochareports",

"pretest": "npm run archive-report && npm run clean:reports",

"scripts": "cypress run --browser chrome",

"combine-reports": "mochawesome-merge ./cypress/reports/chrome/mocha/*.json > cypress/reports/chrome/mochareports/report.json",

"generate-report": "marge cypress/reports/chrome/mochareports/report.json -f report -o cypress/reports/chrome/mochareports",

"posttest-chrome": "npm run combine-reports && npm run generate-report",

"test-chrome": "npm run scripts || npm run posttest-chrome"

cypress.json

"reporter": "cypress-multi-reporters",

"reporterOptions": {

"reporterEnabled": "mochawesome",

"mochaFile": "raports/my-test-output-.xml",

"mochawesomeReporterOptions": {

"reportDir": "cypress/reports/mocha",

"quite": true,

"overwrite": false,

"html": false,

"json": true

} }

simillar: ReportDir of a mochawesome reporter option in cypress.json to point to folder created at run time named after timestamp

I have this fixture that creates the following folder structure:

I have couple of Environment variables set using Jenkins pipeline.

I want to fetch the values of these environment variables in my maven pom.xml file, where I want to pass them as buildArgs to docker-maven-plugin, which will be again called in a dockerfile.

How to call those environment variables in my pom.xml?

I tried ${env.JENKINS_USER_NAME} as well as %JENKINS_USER_NAME% but nothing seem to work.

Use case: I will be running my Jenkins pipeline job to build my project, which will eventually create an docker image in Stage-1 and then run the docker container in Stage-2 (which will run the tests as well internally).

Problem: My Jenkins job can be triggered based on user selection of specific testng.xml file as show below:

When triggered once, it is working fine but if we triggered for second time without cleaning the workspace, then it is throwing error like

I am assuming that it might be a problem with permission, as I am mounting volume to map container test-output directory with Jenkins host-VM directory

How can I get the environment variables in my POM?

I am using Jenkins version of 2.289.3. And I am working on a Maven-TestNG Selenium project in it. I have added Build Timestamp plugin and setup it in Manage Jenkins -> Configure System -> Build Timestamp with a pattern yyyy.MM.dd.HH.mm.ss of Asia/Calcutta. I am using Publish Html reports in Post Build action of that job's configuration. I have given path for HTML directory to archive is:

I'm running a Cypress test in my build pipeline (vmImage: ubuntu-latest) and it exports a video of the test. But the video freezes after 3 seconds (while the video itself is 15 seconds long). Locally the video runs fine. It seems this is an issue when creating the video on a low-end CPU.

I've disabled encoding for the video so it takes less CPU: