Automation testing for MD files

[sambhavgupta0705]

Why do we need this improvement?

Sometimes some MD files doesn't get rendered for which we doesn't get notify .For this we need to setup a workflow which notify us whenever any md files doesn't get rendered .

[lucky29-git]

@sambhavgupta0705 can I work in this issue, if you can guide me a bit?
Do you think creating a github actions workflow will be enough?

[sambhavgupta0705]

@lucky29-git I have submitted this as bounty issue and one of the maintainer will be working on it

[lucky29-git]

Okay sir 🙌,
which Slack channel should I use to ask my questions and connect with you? @sambhavgupta0705

[sambhavgupta0705]

You can start communication on #11 contributing

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q4, bounty/medium, bounty/coding
First assignment to regular contributors: 2024-09-20 00:00:00 UTC+12:00
End Of Life after: 2024-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[anshgoyalevil]

Hey @aeworxet. I would like to take up this issue as a maintainer of this repo.

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2024-09-16	2024-10-07	2024-11-17	2024-10-20	2024-11-03	2024-11-17

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[anshgoyalevil]

Due to a lot of mixed imports (ESM files), We can't really test the jsdom along with node environment. Got this finding after playing around with jest, RTL, and mdx transformer that is transpiling the mdx files along with import imports. We need to halt this issue until #3187 gets completed.

Any opinions? @akshatnema
//cc @aeworxet

[akshatnema]

@anshgoyalevil Can we create this script in a ESM module in a separate folder? If you want, we can have a separate folder with a package.json configured for ESM to test it in a workflow.

Later on, after complete migration in ESM, we can then delete this temporary package.json and will integrate this workflow in existing scripts.

[aeworxet]

@akshatnema, @anshgoyalevil

Has any decision been made regarding this? Will there be a workaround or will there be a halt until the completion of #3187?

[anshgoyalevil]

@aeworxet Akshat and I had a discussion to implement the static testing on md files.

I will be creating the PR soon. There will be no halt thus.