Tests - Githubissues

GregorCH / ipet

Interactive Performance Evaluation Tools for Optimization Software

MIT License

26 stars 6 forks source link

Tests #36

Closed fschloesser closed 6 years ago

fschloesser commented 7 years ago

Especially for ipet-evaluate, there should be tests against mistakes in userinput.

GregorCH commented 7 years ago

Can you be more specific what needs testing? This issue is rather vague.

fschloesser commented 7 years ago

I've wanted this to be here without thinking about it that much. Yes, it needs to be specified better, I guess at least we should check the following:

for each attribute that the user can edit in xml we should check for
- existing but nonsensical values
- nonexisting values / typos
- not specifying the attribute/value pair at all resp. missing, but required, pairs
- misformatted index/defaultgroup
broken xml code
(maybe) special things we assume, e.g. circular dependencies

GregorCH commented 7 years ago

I think there are two levels of testing mentioned that can be treated individually:

XML parsing, making sure that the string input is set correctly
behavior of the objects during the evaluation, regardless whether it was specified as XML or with function calls.

GregorCH commented 6 years ago

I will close this issue because it is not constructive. We both take care during development that necessary tests are added together with the code.