How can the site testing process be improved?

Question

Software testing

Good afternoon, for automated testing, I use the following tools: coverage matrix in excel (set of test cases, tables with starting data, etc.), c# + selenium webdriver, batch script for parallel launch and documentation of results, document with results , bug-tracker. At the moment I have written about 100 cross-browser tests (the average time for passing the test is 1 hour), before leaving work I run all the tests, in the morning I analyze the document with the results and file errors in the bug tracker, the rest of the time I am editing old tests, creating new ones and documenting . Advise what else can be added to the process, what can be improved?

Answer 1

It all depends on what you want to improve.
In isolation from existing problems, there are, in fact, the following areas:
1) Optimization and parallelization of test execution.
The goal is to make test runs faster.
Method - refactoring, parallel launches, optimization in terms of test design.
2) Optimization of the test suite: either in breadth (increase in test coverage) or in depth (more test data and test scenarios)
The goal is to catch more defects.
Method - optimization of test design, generation of new test data.
3) Stability and maintainability. Again refactoring and optimization.
4) Usability. Attaching autotests to build plans, generating reports on their passage, generating defects in the bug tracker during crashes, and more.
In general, tighter integration with the rest of the test infrastructure.
It's like that, offhand.
In general, to say "where to develop" you need to understand what is missing.
Tests are not stable (pseudo-crashes) -> refactor, miss a lot of bugs in the covered functionality -> finish the test suite\test data, spend a lot of time analyzing run results and introducing bugs - optimize test report generation, auto-report to the bug tracker .
Again, if the project often has bugs like "ruled in one place - fell off in another" - you need to update the speed of the run as much as possible and fasten it to the project build plan. We pushed the changes - the tests started.