Quality with nimble speed & DevOps
Projects using waterfalls often have a release cycle
measured in several months (several years even). Agile and Scrum revolutionized
so much in the software by being able to send at the end of each sprint - it
can happen from a week today, even hours in several projects. DevOps often has
automatic deployment scheduled several times per day. This means the level of
change in the production code can be an order of magnitude faster in Devops
than Agile. It sets the stage to provide quality at the speed of DevOps and
agile.
In a nimble world, the team was asked to move faster -
reduce the length of time for delivery while continuing to improve the quality
of each release
Testing is a quality process of lean at each step. It
includes the story of quality users, quality environment, quality test data,
quality unit tests, quality functional tests, and quality performance tests.
We don't compromise between speed and quality
As digital disturbing business, we see the unprecedented speed
requests, while quality, of course, is given; As a result, the old testing the method does not cut it again. We at sapizon, never compromised on quality to
achieve 'speed'.
In Sapizon we achieve quality with speed by applying the
following things
Shift testing left
Our testers involve from the start. Testers join a design
session to ask questions about how customers work, try to find gaps in the
requirements in the user's story, which ultimately leads to design changes. The
others sat with fire developers and decided on the test for new services when they
were developed. But others find themselves paired with UI developers and fire
to test something new on their machines before reaching the building.
Actual testing still occurs in the end, but it will be
smaller and faster because of the problem that you can find before. The left
shift didn't really move closer to the beginning of the release cycle. It
sprinkles every step and every iteration.
In this approach, we have a ready test case when the new
code moves to the QA environment; We just executed test cases related to the
features/stories of Sprint at this time, while we run automatic tests for all
regression testing of the features that have been released. It helped us find
bugs at the beginning of the Sprint cycle, thus giving more time for developers
to fix bugs.
Automation test
We created a reliable and well-maintained automatic test for
all regression areas of past sprints using the latest test automation tools.
We make automatic tests for UI to end the test case, fire
(break, graph, microservices), and DB layers.
To accelerate the development of automation test, we use the
automation framework at home, this also increases the reliability of
the results and maintenance of test execution.
Continuous testing
We integrate automation scripts into CICD pipes (using
device DevOps) and utilize the web cloud platform and cellular devices such as
browsers, lambast, lab sauce, Hobbiton, agricultural AWS devices, etc. To run
an automatic test on various kinds. device combinations and browsers;
It helps us carry out automatic tests early and more often
during the Sprint cycle, this helps us find bugs at the initial stage of the
test cycle.
Susoftware tester companystainable reporting
With the help of device DevOps and test automation, we
publish the results of test execution to various platforms based on client
requirements -
Inbox - The most convenient choice for many of our clients
JIRA-XRAY - We integrate automation tools with Xray GraphQL
API to post results in real-time, so that the entire team will have access to
test reports anytime, anywhere
Practice - We integrate automation tools with fire break
practices to post results in real-time, so that the whole team will have access
to test reports anytime, anywhere
Trail
Quest.
Sustainable integration can help detect faster errors and
complete the way forward in the development process. If a sustainable approach
is not followed, it will take a period of the stretch between integration, which
makes improving this gap longer and a very tense task. This will further reduce
constant broiler to identify problems and more focus on building various
features.
No comments:
Post a Comment