Skip to content

tests

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
TestFunctions.h
TestFunctions.h
 
 
callbacks_call_js_function.cpp
callbacks_call_js_function.cpp
 
 
date_as_function.cpp
date_as_function.cpp
 
 
date_as_new.cpp
date_as_new.cpp
 
 
date_now.cpp
date_now.cpp
 
 
get_property_names.cpp
get_property_names.cpp
 
 
global_return_object.cpp
global_return_object.cpp
 
 
hermesInternal_getInstrumentedStats.cpp
hermesInternal_getInstrumentedStats.cpp
 
 
host_calls_js.cpp
host_calls_js.cpp
 
 
host_calls_js_calls_host.cpp
host_calls_js_calls_host.cpp
 
 
host_calls_js_with_this.cpp
host_calls_js_with_this.cpp
 
 
host_function_caches_object.cpp
host_function_caches_object.cpp
 
 
host_function_creates_objects.cpp
host_function_creates_objects.cpp
 
 
host_function_mutates_global_object.cpp
host_function_mutates_global_object.cpp
 
 
host_function_mutates_object.cpp
host_function_mutates_object.cpp
 
 
host_function_name_and_params.cpp
host_function_name_and_params.cpp
 
 
host_function_return.cpp
host_function_return.cpp
 
 
host_function_return_argument.cpp
host_function_return_argument.cpp
 
 
host_global_object.cpp
host_global_object.cpp
 
 
math_random.cpp
math_random.cpp
 
 
native_property_names.cpp
native_property_names.cpp
 
 
native_sets_constant.cpp
native_sets_constant.cpp
 
 
parse_gc_config.cpp
parse_gc_config.cpp
 
 
surrogate_pair_string.cpp
surrogate_pair_string.cpp
 
 

README.md

Synthetic benchmark replay tests

Each file in this directory is a single integration test for synthetic benchmark parsing and replay.

Adding a new test

Let each test file have a unique identifier, call it testName. Each test file defines two functions:

const char *testNameTrace();
const char *testNameSource();

testNameTrace should return a string of JSON that represents a synthetic trace of a hypothetical native interaction with JS. This interaction can do things like define native functions that are called from JS, or make native objects, or simply call functions in JS. NOTE: The object ids used in the trace string is only meant to be used as a unique identifier, it doesn't have any special meaning. Most tests start at 10 just because of convention. You can use object ids like 3, 400000, or 1345, as long as they are unique integers. NOTE: We use these test traces for two tests each: one uses Strings to represent property names, the other PropNameIDs. To make this possible, we have a "fake" CreatePropNameRecord type. The string substitution in Driver.cpp (where this convention is further explained) leaves changes CreatePropNameRecord into either CreateString or CreatePropNameID, depending on which test variant we're doing. Note that there are CreateStringRecords for strings that are not used as property names; these are left unchanged.

testNameSource is some JS source code that interacts with the native environment created by the trace. It should throw exceptions if the native code does not behave as expected, this will cause the test to fail.

Make sure testName is added to the macro list in TestFunctions.h. Then Driver.cpp will call these new functions for you!

Debugging a broken test

Use gdb, and put a breakpoint on TraceInterpreter::execFunction. Then step through each event that's executed by the interpreter. Currently it's not particularly easy to also debug the JS, that would require a hybrid debugger.