feat(misc): added the automation code for testing of docs

[gautamgambhir97]

• added the automation code for docs testing

[devjsc]

I guess I'm a bit confused, probably needs some discussion; it looks like you're building a unit test per a test per a code block; you're building the website and then getting selenium to hit the copy button, after that you create a file with the python code, and run it with popen.

This of course would work, but feels really wrong 😅 In the short term, could you not iterate over all docs files, looking for python code blocks, and then re-use the logic for popen of the copied string? and test response on that?

I think after this, we'd look to have dedicated unit tests for each code block, but that is involved.

[gautamgambhir97]

there might have been some misunderstanding, i though we have discussed to test the code blocks directly through the website using selenium.

can you please share what could go wrong with the current approach? since we will have to include the test cases for the individual files manually whenever there is new code block, i guess the either approach will behave the same?

Although, i have shared you the list of approaches to you in the personal message, what you are saying is there in the second point. can you please verify the approach?

[devjsc]

Sorry if there has been a misunderstanding, and you're right to have gone forward without some clear direction from me :) I get a lot of messages and some things slip by 👎

There isn't something wrong with this, I just think booting up the site, and running selenium is excessive.