[
https://issues.apache.org/jira/browse/HDDS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855940#comment-16855940
]
Eric Yang edited comment on HDDS-1554 at 6/4/19 5:40 PM:
---------------------------------------------------------
{quote}Based on my experience it can be executed in jenkins without any
problem. I think it works very well without robot test plugin. It's enough to
run robot tests in a dind image. Isn't it?{quote}
No, it would be very difficult to look at the console output look to determine
which test case has failed because FAIL is a common word in the output. Color
coding in test summary report is very useful to identify the failed test case
with a single glance. Jenkins Robot framework plugin also helps to organize
build number and generated report.
{quote}Can you please explain how the junit test will do it if the backend runs
in a spearated container?{quote}
Junit tests can be written to interact with rpc, http to retrieve information
from backend that runs in a separate container. Exception Wrapping can handle
server side stack trace to provide seamless experience without additional
coding.
Seasoned programmer maybe interested in remote debugging to capture private
variable states, remote debugger parameters can be passed as environment
variable to JAVA_OPTS for docker container:
{code}-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y{code}
This allows IDE to connect to containerized server for troubleshooting, while
launching Junit tests that are interacting with the container. This
arrangement can cover most of end to end white box testing with power of IDE to
assist remote debugging.
was (Author: eyang):
{quote}Based on my experience it can be executed in jenkins without any
problem. I think it works very well without robot test plugin. It's enough to
run robot tests in a dind image. Isn't it?{quote}
No, it would be very difficult to look at the console output look to determine
which test case has failed because FAIL is a common word in the output. Color
coding in test summary report is very useful to identify the failed test case
with a single glance. Jenkins Robot framework plugin also helps to organize
build number and generated report.
{quote}Can you please explain how the junit test will do it if the backend runs
in a spearated container?{quote}
Junit tests can be written to interact with rpc, http to retrieve information
from backend that runs in a separate container. Exception Wrapping can handle
server side stack trace to provide seamless experience without additional
coding.
Seasoned programmer maybe interested in remote debugging to capture private
variable states, remote debugger parameters can be passed as environment
variable to JAVA_OPTS for docker container:
{code}-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y{code}
This allows IDE to connect to containerized server for troubleshooting, while
launching Junit tests are interacting with the container. This arrangement can
cover most of end to end white box testing with power of IDE to assist remote
debugging.
> Create disk tests for fault injection test
> ------------------------------------------
>
> Key: HDDS-1554
> URL: https://issues.apache.org/jira/browse/HDDS-1554
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: HDDS-1554.001.patch
>
>
> The current plan for fault injection disk tests are:
> # Scenario 1 - Read/Write test
> ## Run docker-compose to bring up a cluster
> ## Initialize scm and om
> ## Upload data to Ozone cluster
> ## Verify data is correct
> ## Shutdown cluster
> # Scenario 2 - Read/Only test
> ## Repeat Scenario 1
> ## Mount data disk as read only
> ## Try to write data to Ozone cluster
> ## Validate error message is correct
> ## Shutdown cluster
> # Scenario 3 - Corruption test
> ## Repeat Scenario 2
> ## Shutdown cluster
> ## Modify data disk data
> ## Restart cluster
> ## Validate error message for read from corrupted data
> ## Validate error message for write to corrupted volume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
