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

Details how to use evomaster + info on found faults #765

Open
bungdanar opened this issue May 17, 2023 · 8 comments
Open

Details how to use evomaster + info on found faults #765

bungdanar opened this issue May 17, 2023 · 8 comments

Comments

@bungdanar
Copy link

Hi, I'm currently trying evomaster to do blackbox testing on a RESTful API written in the NodeJs and Python programming languages. I'm using evomaster via windows installer.

I've tried running evomaster for 15 minutes and managed to generate tests. After the tests have been generated, should I run the tests? And how do I install dependencies to be able to run the tests?

@arcuri82
Copy link
Collaborator

hi.
by default, tests are generated in Java for JUnit. If you using NodeJS, can try the experimental option --outputFormat=JS_JEST

@bungdanar
Copy link
Author

Hi, thank you so much for the answer. I was finally able to run the JUnit tests after installing the required dependencies although it was quite difficult as I don't have much experience in the Java ecosystem.

I actually will use evomaster for my thesis paper. How do we know how many bugs the evomaster has found? For example, if there are 2 tests in the EvoMaster_faults_Test.java file, does that mean that evomaster has found 2 bugs?

@arcuri82
Copy link
Collaborator

hi.
on the console, you get the info Potential faults: .... But, indeed, we should provide better information in the generated EvoMaster_faults_Test files

@arcuri82 arcuri82 changed the title Details how to use evomaster Details how to use evomaster + info on found faults May 19, 2023
@arcuri82
Copy link
Collaborator

you can also use --writeStatistics=true, and check the potentialFaults column there in the generated CSV file

@bungdanar
Copy link
Author

There is no information about Potential Faults in the console output. Maybe I missed a certain option parameter.

em-consolo-output

But the information about Potential Faults exists in the statistics.csv file

em-statistic-output

Anyway, thank you very much for the response.

@arcuri82 arcuri82 added the bug label May 19, 2023
@arcuri82
Copy link
Collaborator

it is a bug, as it looks like we print it only for White-Box testing, but not for Black-box

@wanglewang
Copy link

--writeStatistics=true

if a api need auth token,how add token to testcases

@alegonzalezz
Copy link

@wanglewang I have the same problem. Can did You fix it?

onurd86 added a commit that referenced this issue Jan 22, 2024
#765

I commented some code in Main since not sure if they were safe to remove.

I wrote one test for the fix but takes a bit time.
arcuri82 added a commit that referenced this issue Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants