Michael added a comment.

  **⚠️ WIP ⚠️**
  
  |                                                                             
                        | Async Webdriver                                       
                                                                          | 
Cypress                                                                         
                                                                                
                                              |
  | What setup costs does each approach incur?                                  
                        |                                                       
                                                                          |     
                                                                                
                                                                                
                                          |
  | How compatible is each approach with our current CI?                        
                        | Very, it might even support runnning tests of a 
single suite in parallel? T226869 <https://phabricator.wikimedia.org/T226869>   
                                                  | Running tests of a single 
suit in parallel is probably not possible, because it requires orchestration by 
an external cypress.io service. It might be possible with GitLab CI though, 
once we migrated there. |
  | How performant is each approach, both locally and on CI servers?            
                        |                                                       
                                                                          |     
                                                                                
                                                                                
                                          |
  | How does the chosen approach impact onboarding efforts for new developers?  
                        | Pausing a test to interact with a page is always a 
hazzle. Window closes after test is done. No "interactive" way to run tests. | 
Writing new tests is easy, because Cypress is keeps the window open with 
dangling state to allow for interacting with the system after the test 
finished.                                                     |
  | How documented is each approach to support possible future troubleshooting 
and development efforts? |                                                      
                                                                           |    
                                                                                
                                                                                
                                           |
  |

TASK DETAIL
  https://phabricator.wikimedia.org/T331732

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Michael
Cc: Michael, Aklapper, ItamarWMDE, Astuthiodit_1, karapayneWMDE, Invadibot, 
maantietaja, SCIdude, Akuckartz, pdehaye, Nandana, Lahi, Gq86, Andrawaag, 
GoranSMilovanovic, QZanden, YULdigitalpreservation, LawExplorer, Salgo60, 
_jensen, rosalieper, Scott_WUaS, MisterSynergy, abian, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331
_______________________________________________
Wikidata-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to