Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the purpose of the output-expected folder? #4

Open
zzctmac opened this issue Sep 22, 2024 · 0 comments
Open

What is the purpose of the output-expected folder? #4

zzctmac opened this issue Sep 22, 2024 · 0 comments

Comments

@zzctmac
Copy link

zzctmac commented Sep 22, 2024

Hi, I am using this fantastic tool to check my promise codes. But I am wondering what the purpose of the output-expected folder is.
For example, I have a code snippet:

function getFromApi(p) {
    return {'p': 1}
}
var performancePerMonth = new Promise(function(resolve, reject) {
    var path = some_path;
    getFromApi(path);
});

And I run this code snippet with the following setup:

function runTestsOnlyWithJalangi(testName){
    it(testName + '(runJalangi)', function (done) {                                 
        this.timeout(10000);
        common.runJalangi(testName, INPUT_DIR, ACTUAL_OUTPUT_DIR);
        done();
    });
}

I can get the promise graph, and it finds the unsettled promise:
stackoverflow_41268953 js

In this process, I do not have an output-expected file to run with the following setup:

 it(testName + '(checkoutput)', function (done) {                              
        common.checkGeneratedCode(testName, ACTUAL_OUTPUT_DIR, EXPECTED_OUTPUT_DIR);
        done();
    });
    it(testName + 'checkGraph', function (done) {
        common.checkGeneratedGraph(testName, ACTUAL_OUTPUT_DIR, EXPECTED_OUTPUT_DIR);
        done();
    });

Hence, I would like to know the purpose of the output-expected folder. Is it necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant