[ 
https://issues.apache.org/jira/browse/CAMEL-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Istomin updated CAMEL-15661:
----------------------------------
    Description: 
Currently there are:
 # unit-tests
 # integration tests, that runs manually using real cloud azure services (need 
to specify `accountName`, `accessKey`)

Proposal:
 # Use Testcontainers and Azurite for integration tesing
 # Reuse integration tests codebase
 # Enable testcontainers integration tests by default
 # Do not remove possibilty to run integration tests on cloud azure services 
using different maven profile

  was:
Currently there are:
 # unit-tests
 # integration tests, that runs manually using real cloud azure services (need 
to specify `accountName`, `accessKey`)

Proposal:
 # Use Testcontainter and Azurite for integration tesing
 # Reuse integration tests codebase
 # Enable testcontainers integration tests by default
 # Do not remove possibilty to run integration tests on cloud azure services 
using different maven profile


> [camel-azure-strorage-blob] Use Testcontainers and Azurite at integration 
> tests
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-15661
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15661
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-azure
>    Affects Versions: Future
>            Reporter: Denis Istomin
>            Assignee: Denis Istomin
>            Priority: Major
>             Fix For: Future
>
>
> Currently there are:
>  # unit-tests
>  # integration tests, that runs manually using real cloud azure services 
> (need to specify `accountName`, `accessKey`)
> Proposal:
>  # Use Testcontainers and Azurite for integration tesing
>  # Reuse integration tests codebase
>  # Enable testcontainers integration tests by default
>  # Do not remove possibilty to run integration tests on cloud azure services 
> using different maven profile



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to