Test collaborative Experiment Tracking

[rashidakanchwala]

Description

This ticket is to test collaborative experiment tracking functionality that will be build here #1295 . The ticket will include

• Robustness tests to ensure the feature is stable and can handle various inputs and scenarios.
• Stress testing to ensure the feature works with large number of users and heavy load.
• Testing across multiple cloud storages (s3, azure blob, gcs etc.)

[rashidakanchwala]

The below tests to check for robustness have successfully passed. The tests were done with 3 users.

• Kedro Run (non-simultaneously)
• Kedro Run (simultaneously)
• Running Kedro viz (non-simultaneously)
• Running Kedro-viz (simultaneously)
• Kedro-run while someone is running Kedro-viz.
• Multiple Kedro-runs while someone is running Kedro-viz (simultaneously)
• Kedro-run while two people are running Kedro-viz (simultaneously)
• One person is on Kedro-viz, One person is modifying title on Kedro-viz, One person is doing Kedro-run
• One person is on Kedro-viz, One person is modifying notes on Kedro-viz, One person is doing Kedro-run
• One person is on Kedro-viz, One person is bookmarking on Kedro-viz, One person is doing Kedro-run
• Two people running collab experiment tracking, one person running only local for same project
• All 3 users delete local session_store.db. Expected Results - All their modified changes disappear but they can still see all the runs