Difference between revisions of "PKC documentation"
| Line 20: | Line 20: | ||
===Testing - use implement | ===Testing - use implement selenium on our DDT protocol=== | ||
- Selenium is exposing username and password for tester user, will need to find good way to do login | - Selenium is exposing username and password for tester user, will need to find good way to do login | ||
- So far, as observe, our preliminary conclusion regarding the login issue is due to failed session sync between mediawiki and PKC. | - So far, as observe, our preliminary conclusion regarding the login issue is due to failed session sync between mediawiki and PKC. | ||
Revision as of 14:42, 4 September 2022
The current page is dedicated to PKC Team process of documentation since the Week35 of 2022
Week35 of 2022 (29/08 to 02/09)
Meetings
progress discussion - planning vs ongoing progress
https://pkc.pub/wiki/File:Progress_discussion_-_planning_vs_ongoing_progress-20220830_130820.mp4
Video:Progress_discussion_-_planning_vs_ongoing_progress-20220830_130820.mp4
Video:Video's Name Here or <video name="Progress_discussion_-_planning_vs_ongoing_progress-20220830_130820.mp4"/>.
Testing - use implement selenium on our DDT protocol
- Selenium is exposing username and password for tester user, will need to find good way to do login - So far, as observe, our preliminary conclusion regarding the login issue is due to failed session sync between mediawiki and PKC. - How to re-create. - ensure clear history - ensure logout from github - Do Login at PKC, using keycloak + github - while the web browser is opened, put machine to sleep - after 10-20 seconds or so, try to refresh PKC’s screen - will displayed Error
Closure Meeting (lessons learned, replanning next week, validation)
https://pkc.pub/wiki/File:Closure_Meeting_(lessons_learned,_replanning_next_week,_validation)-20220902_143424.mp4 https://pkc.pub/wiki/File:Closure_Meeting_(lessons_learned,_replanning_next_week,_validation)_part2_-20220902_143424.mp4