Skip to content

Latest commit

 

History

History
 
 

jit

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
CMakeLists.txt
CMakeLists.txt
 
 
README.md
README.md
 
 
__init__.py
__init__.py
 
 
gtest.cpp
gtest.cpp
 
 
test_alias_analysis.cpp
test_alias_analysis.cpp
 
 
test_argument_spec.cpp
test_argument_spec.cpp
 
 
test_autodiff.cpp
test_autodiff.cpp
 
 
test_base.cpp
test_base.cpp
 
 
test_base.h
test_base.h
 
 
test_class_import.cpp
test_class_import.cpp
 
 
test_class_parser.cpp
test_class_parser.cpp
 
 
test_class_type.cpp
test_class_type.cpp
 
 
test_code_template.cpp
test_code_template.cpp
 
 
test_constant_pooling.cpp
test_constant_pooling.cpp
 
 
test_create_autodiff_subgraphs.cpp
test_create_autodiff_subgraphs.cpp
 
 
test_custom_class.cpp
test_custom_class.cpp
 
 
test_custom_operators.cpp
test_custom_operators.cpp
 
 
test_dce.cpp
test_dce.cpp
 
 
test_fuser.cpp
test_fuser.cpp
 
 
test_gpu.cpp
test_gpu.cpp
 
 
test_graph_executor.cpp
test_graph_executor.cpp
 
 
test_inliner.cpp
test_inliner.cpp
 
 
test_interface.cpp
test_interface.cpp
 
 
test_interpreter.cpp
test_interpreter.cpp
 
 
test_ir.cpp
test_ir.cpp
 
 
test_irparser.cpp
test_irparser.cpp
 
 
test_jit_type.cpp
test_jit_type.cpp
 
 
test_lite_interpreter.cpp
test_lite_interpreter.cpp
 
 
test_misc.cpp
test_misc.cpp
 
 
test_mobile_type_parser.cpp
test_mobile_type_parser.cpp
 
 
test_module_api.cpp
test_module_api.cpp
 
 
test_peephole_optimize.cpp
test_peephole_optimize.cpp
 
 
test_qualified_name.cpp
test_qualified_name.cpp
 
 
test_save_load.cpp
test_save_load.cpp
 
 
test_schema_matching.cpp
test_schema_matching.cpp
 
 
test_subgraph_matcher.cpp
test_subgraph_matcher.cpp
 
 
test_subgraph_rewriter.cpp
test_subgraph_rewriter.cpp
 
 
test_subgraph_utils.cpp
test_subgraph_utils.cpp
 
 
test_utils.cpp
test_utils.cpp
 
 
test_utils.h
test_utils.h
 
 
tests.h
tests.h
 
 
tests_setup.py
tests_setup.py
 
 
torch_python_test.cpp
torch_python_test.cpp
 
 

README.md

JIT C++ Tests

How to add a new test

First, create a new test file. Test files should have be placed in this directory, with a name that starts with test_, like test_foo.cpp.

Here is an example test file you can copy-paste.

#include <test/cpp/jit/test_base.h>

// Tests go in torch::jit
namespace torch {
namespace jit {

// 1. Test cases are void() functions.
// 2. They start with the prefix `test`
void testCaseOne() {
    // ...
}

void testCaseTwo() {
    // ...
}
}
}

Then, register your test in tests.h:

// Add to TH_FORALL_TESTS_CUDA instead for CUDA-requiring tests
#define TH_FORALL_TESTS(_)             \
  _(ADFormulas)                        \
  _(Attributes)                        \
  ...
  _(CaseOne)  // note that the `test` prefix is omitted.
  _(CaseTwo)

We glob all the test files together in CMakeLists.txt so that you don't have to edit it every time you add a test. Unfortunately, this means that in order to get the build to pick up your new test file, you need to re-run cmake:

python setup.py build --cmake

Why do we have two different test runners?

We have two different ways of running our cpp tests:

  1. With gtest, from a standalone binary.
  2. With Python, from TestJit.test_cpp and TestJit.test_cpp_cuda (in test/test_jit.py)

We want both because we need to test things from a pure-C++ environment and with all our various Python patch-points enabled.

How do I run the tests?

The following commands assume you are in PyTorch root.

  1. With gtest: 
    # (re)build the test binary
ninja build/bin/test_jit
# run
build/bin/test_jit --gtest_filter='glob_style_filter*'
  2. With Python: 
    python test/test_jit.py TestJit.test_cpp TestJit.test_cpp_cuda