{"id":1629,"date":"2020-02-20T15:20:24","date_gmt":"2020-02-20T09:50:24","guid":{"rendered":"https:\/\/coforge.site\/cigniti\/blog\/?p=1629"},"modified":"2022-07-29T11:43:43","modified_gmt":"2022-07-29T06:13:43","slug":"importance-shift-left-shift-right-testing-approaches","status":"publish","type":"post","link":"https:\/\/coforge.site\/cigniti\/blog\/importance-shift-left-shift-right-testing-approaches\/","title":{"rendered":"The importance of Shift-Left and Shift-Right testing approaches"},"content":{"rendered":"

Edwards Deming had it right when he said, \u201cQuality is everyone\u2019s responsibility\u201d.<\/span><\/b>\u00a0<\/span><\/p>\n

Quality of a product or service is seldom by chance. It can only be achieved through detailed planning and careful execution. Despite the efforts put in, except for in an ideal scenario, there are still bound to be glitches. However, the thing about Quality Assurance (QA) is that it paves the way for higher efficiency and better performance through incessant testing.<\/span>\u00a0<\/span><\/p>\n

With<\/span>\u00a0the implementation of Agile and DevOps methods,\u00a0<\/span>there is a high collaboration among teams<\/span>. Developers are\u00a0<\/span>involved<\/span>\u00a0<\/span>within<\/span>\u00a0a testing cycle right from the early stages. Formerly, the process of testing happened at definite intervals and testers had to wait for the product to be completely built before they set out to find the bugs and glitches. Admittedly, more time than can be agreed upon was spent waiting for the code to come through to a tester\u2019s lap.<\/span>\u00a0When it finally came, there was no<\/span>t<\/span>\u00a0sufficient time left to perform comprehensive testing, which would lead to bug-infested releases into production.<\/span>\u00a0With the drastic change in the role of a tester, the scope for QA has broadened by leaps and bounds. Be it a software-developer-in-test (SDET) or a QA engineer, as a member of a collaborative team, a modern day\u2019s tester has a cadence similar to that of a software development engineer.<\/span>\u00a0<\/span><\/p>\n

An SDET or a QA engineer would be able to easily validate fields being coded in order to avoid data loss. The QA engineer would also be able to write some basic checks and test ideas for an application programming interface (API), all of which inherently improves the design. Having teams that test earlier in the application lifecycle helps the QA engineers feel far more at ease with tooling and technology. Being able to look through server processes, work with API tools, or just walk through code quickly with a bit of help, is rapidly becoming a desired (and a much-required) skill.<\/span>\u00a0<\/span><\/p>\n

When speaking of quality software based on\u00a0<\/span>the software development<\/span>\u00a0processes, there are two essential parameters (among a few others) one should consider:<\/span>\u00a0<\/span><\/p>\n