I don't see why not
from my limited experience with it that seems to be the intended response
I was struggling to use VCRpy or our request mocking because some of the URLs include a randomised UUID which changes every time! WHyyyyyyy!
That seems like a great Microsoft idea 😄
We were struggling with getting logs from azure because Microsoft decided to make one part of the storage url random 🤦♂️
But maybe they did implement some useless thing like again I. Azure it seems that they take a screen shot of the file in storage. Because when you are storing text files you really need a screenshot with the first logs 🤣
All the urls have that UUID?
It seems like when creating a message with Teams you POST to a URL with a randomised uuid on the end, that UUID becomes the UUID of the message. But it's the local SDK that created the UUID, which is a bit weird IMO. usually you would just post to some generic endpoint and the server side creates the UUID and returns it in the response.
So using VCR to record call fails because that URL changes every time you run the tests. I guess I'll need to implement a custom handler, but thats just annoying.
I replied to this in the Teams PR. I think you could add a pytest fixture that generates a consistent list of UUIDs.
Ajit D'Sa and I have been working on some DB updates. Updated MongoDB, added a postgres, but also we could update SQLite.
The main reason is this:
Skills should be allowed to specify which table they save to.
Right now, one opsdroid instance with one DB, two different skills will save into the same table/collection of the same db.
So we allow:
- setting default table name in DB
- depending on skill, allowing default table (or tables) name in skill config
- setting table name in the
putandgetfunctions as an optional kwarg.
I do not know how to write good tests for this. Is there a way to spin up a postgres instance on commit and run unit tests against it? Or decent mock modules available?
Awesome thanks! I'm excited to see this work happening.
I'm curious about the desire to have different tables/collections for each skill. I've always considered it a feature that the opsdroid memory object is accessible from any skill. Each skill can just choose a prefix for the key name if there are concerns about collision.
1 reply
For testing you might want to look into
pytest-docker to start a postgres database as part of the pytest fixtures.
1 reply
I think it would be good if you could open an issue to discuss the table per skill idea. Then we can keep all the conversation about it there.
1 reply
I just want to take a minute to highlight that we have a community code of conduct. Everyone engaging in discussion anywhere in the opsdroid community is expected to follow these standards. I am super excited by the recent surge in activity and having folks improve opsdroid. Let's make this this is a fun and positive environment for everyone. https://github.com/opsdroid/opsdroid/blob/master/CODE_OF_CONDUCT.md
It's really easy to get someone defensive when people start asking for changes in what they have been working on for a while now. So in this case it's not entirely on dud here. Not to bring this down that path but just wanted to bring that up.
I hadn't targeted that at anyone in particular. There has just been a general vibe for a while lately that I wanted to get ahead of.
I'm aware that I can be a little blunt in my reviews, so it's a good reminder for myself too.
I just want to say that I appreciate all you guys, the time you take and spend on this, your feedback, and your opinions. So far I feel that all of it comes from a good place, and that I also appreciate Jacob Tomlinson's efforts to make sure it stays that way. Thanks to all of you.
Woohoo! I just merged the teams PR! Thank you Jacob Tomlinson and FabioRosado for figuring out how to add teams support!
Thanks for all the help reviewing. And your work on the test machinery. Tests have been the main blocker for the PR (and time) but that was a joy to test.
Maybe I'm missing something, but if I change this line https://github.com/opsdroid/opsdroid/blob/master/opsdroid/connector/github/tests/test_connector_github.py#L237 to
assert event.abc == "pyup-bot" and then run pytest opsdroid/connector/github/tests/test_connector_github.py::test_pr_merged it still passes. Any reason why this would be?
Oooh interesting. I think because the assertions are inside the skill they get ignored.
We log exceptions in skills and move on. Don't want user code to cause the whole thing to die. https://github.com/opsdroid/opsdroid/blob/a45490d1bdceca39b49880e20262b55ea0be101d/opsdroid/core.py#L466
So we should probably be asserting that
Exception when running skill is not logged once the skill has been run.
Good catch thanks!
Yes, that totally makes sense. Hmmmm, I understand this, but in terms of implementation, that's like saying we should put the
call_endpoint in a try and then catch the exception coming back, yah? If not, lemme know if you can pseudocode it out for me, and I'll try making the change
We need to add
caplog to the arguments here https://github.com/opsdroid/opsdroid/blob/a45490d1bdceca39b49880e20262b55ea0be101d/opsdroid/connector/github/tests/test_connector_github.py#L227
Then add
assert "Exception when running skill" not in caplog.text here https://github.com/opsdroid/opsdroid/blob/a45490d1bdceca39b49880e20262b55ea0be101d/opsdroid/connector/github/tests/test_connector_github.py#L249
Oho. Okay, I'll see if I can get that working for you. Thanks for much for the pointer.... learning :)
We probably need to do this in every test that has assertions inside the skill
Jacob Tomlinson: so I am not convinced the skill-based tests are working. Here is what I mean by this... I couldn't get the
caplog stuff working. But I read all about caplog and there's no reason it shouldn't work. So I tried just straight raising an exception in the skill, and finally just tried putting a breakpoint (like a pdb.set_trace()) in the skill... and none of it registered. There didn't seem to be any change I could make in the skill that would affect anything at all. I tried this with multiple skills. I only tried this with skills in the github connector so far.