Open tony-shannon opened 4 years ago
comment from Bogdan
Step 1: we create tests for each page (only check that this link is available and page title is presented) - 2-3 h Step 2: check functionality (Create/Edit/Show, Chart/Table switching etc.) of each page separately (depends on page - for BI, Vitals and Allergies)
Suggest complete Step 1 and after this solve, which pages we will check more detail
ok need full estimate for Step 2 and means to deploy this tests online even if we need to use TeamCity for now
OK! According to test deploy - I need in Vladimir's help. I can create test and check it locally, but I don't know, how to deploy it.
About estimation. We created Create/Update tests for TopThreeThings (for Helm) - so, we can do this.
Suggest try to create Create/Update for all our plugins during 8-10h.
#######
@kuvakina to update with a brief plan please
@tony-shannon I'm not sure about plan, but as we have the issues with E2E tests right now, I can make some notices that we maybe should keep in mind:
Form QA who created the E2E tests before, I heard that the biggest problem with tests was the fact that the staging could not withstand the speed with which tests in 1 stream sent requests. It's a system problem. The problem should be solved with good infrastructure and good DevOps.
When creating tests, check that smtp closed from outside.
Problem with tests could be also when Jenkins connect to VNC.
Need to revisit E2E tests for Showcase Dev RA + Qewd + EtherCIS stack