reuse/api
9
3
Fork 2
Code Issues 38 Pull Requests 2 Activity

Automated test suite #16

New Issue
Closed
opened 2019-08-07 16:47:20 +00:00 by reinhard · 4 comments
reinhard commented 2019-08-07 16:47:20 +00:00
Member
Copy Link
Copy Source

For a public service like this, we probably want an automatic test suite to ensure that at least no completely broken code is deployed. I see that the slots for black and pytest based quality checks are already prepared, so I'm posting this issue as a reminder to fill them. :-)

For a public service like this, we probably want an automatic test suite to ensure that at least no completely broken code is deployed. I see that the slots for black and pytest based quality checks are already prepared, so I'm posting this issue as a reminder to fill them. :-)
florian.vuillemot was assigned by max.mehl 2020-12-04 10:25:57 +00:00
max.mehl commented 2020-12-04 10:40:53 +00:00
Owner
Copy Link
Copy Source

Also adding here that pytest shows a lot of errors, so we may want to go through them.

Also adding here that pytest shows a lot of errors, so we may want to go through them.
florian.vuillemot commented 2021-09-17 07:29:38 +00:00
Member
Copy Link
Copy Source

I'm not sure how to test the whole application, especially because of the FORMS dependency. Do you have an idea?

But, I can do a unit test on scheduler to start.

I'm not sure how to test the whole application, especially because of the FORMS dependency. Do you have an idea? But, I can do a unit test on `scheduler` to start.
reinhard commented 2021-09-18 16:27:28 +00:00
Author
Member
Copy Link
Copy Source

I think the best method is to create mock replacements for the forms functions.

I think the best method is to create mock replacements for the forms functions.
:+1: 1
florian.vuillemot commented 2022-02-06 18:48:17 +00:00
Member
Copy Link
Copy Source

Do you have any ideas for other tests?

Do you have any ideas for other tests?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.0
Problems that do not concern the 2.0 rewrite, probably should be ignored
component
backend
Issues concerning the backend (logic connecting frontend with the database)
component
database
Issues concerning the database
component
docs
Issues regarding documentation
component
frontend
Issues concerning the frontend
prio
high
High priority
prio
low
Low priority
prio
maybe
Lowest priority
prio
mid
Medium priority
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
carmenbianca (carmenbianca) fkobi (Filip Kobierski) florian.vuillemot (florian.vuillemot) floriansnow (Florian Snow) git-robot linus (Linus Sehn) max.mehl (Max Mehl) nico.rikken (nico.rikken) reinhard (Reinhard Müller) renovate-bot (Renovate Bot) tobiasd (tobiasd)
No Assignees florian.vuillemot
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: reuse/api#16