Open kuvakina opened 6 years ago
To provide more insight for the external developers and any other stakeholders additional documents will be created. First of all, Unit and E2E Tests designation, structure and implementation are going to be described as these areas are potentially the most complex ones for a newcomer to grasp.
These records will contain (but not limited to) the following sections:
1) The reasoning behind utilizing a testing approach (unit or e2e)
2) The main description of tests functioning
3) Tests folder structure and architecture
4) Testing tools (Nightwatch.js, jest, etc.) and execution environment
5) Exemplary code and logic flow of a single test or a couple of them
ok thanks for update , look forward to that documentation, thanks
@tony-shannon
Here is a draft version of the documentation, please has a look, Tony.
If you have any ideas or want anything to be changed, I'll appreciate if you write it here.
ok this looks excellent Yet if anything it looks overdetailed and going to be hard to maintain In particular those flowcharts will be a real ordeal to maintain Can you simplify those please with something we can use with github markdown? thanks Tony
Thank you for your feedback, Tony.
Ok, we simplify the documentation and come back to you with a new version.
@tony-shannon
this approach needs updating to account for different Showcase and Helm E2E tests, probably in 2 seperate repos
I understand @tony-shannon
Thank you
Create Wiki for End2End Testing documentation and add it here: https://github.com/PulseTile/PulseTile-Docs/wiki