EgorBaranovEnjoysTyping commented on code in PR #13285:
URL: https://github.com/apache/ignite/pull/13285#discussion_r3821149168


##########
modules/ducktests/DEV_GUIDE.md:
##########
@@ -0,0 +1,518 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+# How to Write a New DuckTest
+
+The ignite-ducktests framework is a bilingual integration testing framework:
+
+| Layer                | Language | Purpose                                    
                       |
+|----------------------|----------|-------------------------------------------------------------------|
+| Test orchestration   | Python   | Manages Docker containers, starts/stops 
nodes, asserts results    |
+| In-cluster workloads | Java     | Runs inside Ignite nodes (cache ops, 
transactions, queries, etc.) |
+
+Each Ignite node runs in a separate Docker container. The Python layer manages 
container lifecycle and simulates network failures via iptables.
+
+---
+## Write a Java Application (if needed)

Review Comment:
   Intentional: the Java section is marked "(if needed)" — readers who only 
need a Python wrapper can skip it. The Python test references the Java class by 
`java_class_name`, so it makes sense to see what Java class you're wiring in 
before writing the Python side.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to