White Paper: Automated Database Testing Step up Your Data Potential Table of Contents

Total Page:16

File Type:pdf, Size:1020Kb

White Paper: Automated Database Testing Step up Your Data Potential Table of Contents White Paper: Automated Database Testing Step up your Data Potential Table of Contents Executive Summary Understanding the Significance of Database Testing Importance of an Automation Strategy for Database Testing Life Cycle of Automation Database Testing Why Database Automation is Necessary to Solve Common Challenges What Can Be Automated in Database Testing? Conclusion Executive Summary With varying complexities and heterogeneous environments, companies utilize different forms of strategies and tests in place. It could be manual testing, it could be automated testing and it could be the combination of both. In this age, wherein we talk about data size in terabytes, it is really difficult to form the testing strategy based on manual testing. We need to have some form of automation for sure in database testing. This white paper takes through the journey of Automated Database Testing to step up your data potential. 1 2 Understanding the Significance of Database Testing Data is undoubtedly critical from a techno-commercial point of view. All companies, ranging from e-commerce to pharmaceutical and banking to insurance companies have data as their asset. Testing this segment is really critical and it involves testing strategies such as quality control and quality assurance of the product databases. All the companies which deals with or which are associated with data warehousing or data storage, need to have an indestructible and a coherent database system. If database processes such as Select, Update, Insert & Delete are performed without testing the database for consistency first, the organization risks a crash and chaos of the entire system. The formal approach of testing may not be adequate in which programmers formally test the databases or QA engineers wait for managers to call upon consultants. Finally, database testing mainly deals with finding errors in the databases so as to eliminate them, be it at data level or structure level. The final outcome after testing will improve the quality of the database to serve mission critical systems. How many times it would happen that the code changes have been deployed to the production server, but schema changes are not rolled out and it has resulted in chaos? How many times you could not reproduce the scenarios on test servers that is producible on production servers? It is data which can be the culprit. It is important for companies to have answers to common questions like – How do we make sure that the rights given to some user temporarily has been rolled back or not? Are we running over allocated quotas on some database objects or not? Are all the developers following the database coding standards that we have set? All these are covered as part of continuous activity and falls under database testing or data validation testing or database health testing. Thus, a sound database testing strategy helps companies to avoid the chaos and repercussions. Importance of an Automation Strategy for Database Testing It is vital to understand the importance of an Automation Strategy for Database Testing and considerations while forming these strategies. The parameters to consider could be among nature of application under test, environment to be used, stakeholders’ expectations and of course overall ROI by doing this automation. Executing tests partially or repeating tests unnecessarily can cost you huge. It’s vital to identify regular database tests to cover data validation, schema verification, security checks, data certification and cross checking with UI test results. Every strategy in IT revolves around cost, time and quality and hence while building any strategy, a lot of aspects needs to be considered. The stakeholders may not want to invest into a strategy which might cover everything but takes a lot of time and hence cost. At the same time, they cannot afford loose 2 ends for the most critical business functions which drives their branding and revenue. With this thumb rule in consideration, it would be wise to build a strategy which is based on Risk- based testing (RBT). The wiki definition for RBT goes like this “RBT is a type of software testing that functions as an organizational principle used to prioritize the tests of features and functions in software, based on the risk of failure, the function of their importance and likelihood or impact of failure”. This means that, we identify the scope of an entire application, put ranking on the scale of 1-5 (5 most critical) against each module and do the automation only for those modules which are most critical as per business. However, database testing should be differentiated from strategies to deal with other problems such as database crashes, failovers, broken insertions, deletions or updates. Life Cycle of Automation Database Testing Test Script Identify Scope Data Certification Execution Preparation Cross-check with Integration with Post Execution Reporting UI Testing Report Scheduled Jobs Monitoring 1. Identify Scope The first thing is to identify what all to be covered, what can be excluded and which all modules are impacting the business most. Aspects like data verification, schema verification, health checks, database guideline checks, security checks and a lot more can be clubbed together here. 2. Test Script Preparation This step is really tricky, it deals with preparation for test scripts and hence, lot of judgments to be taken here. Firstly, identify automation tool to be used based on criteria like licensing cost, time to do the automation, support provided out of the box by the tool for various integrations, support offered by the vendor, scalability for test scripts and a lot more. Once finalized with tool, grab needful SQL queries to be executed, identify conditional flows and prepare automation scripts. Always keep in consideration that versioning helps. Make sure you prepare test environment to execute tests here. 3 3. Data Certification This step is to identify the potential test cases to carry out data checks among query to query or query to previously stored data. Prepare needful batches in case there is a huge data. Make it flexible enough so that a few test cases are testing abstract details while others can dig it till row level comparison. 4. Execution Execute scripts you have prepared here and tweak them to perform as expected. Add needful conditional flows, loop around to use the same case for multiple sets of data and make them more robust. Identify repeated scripts and make code maintenance-friendly right at initial stage. 5. Reporting The outcome of the test execution is monitored here. There is no point in digging through logs for all kinds of reporting. Add needful automation steps to generate charts for managers and detailed logs for developers. 6. Post Execution Monitoring Monitoring the trends of execution and doing fixes if any, to test scripts. This is a continuous activity and needs to be performed multiple times to conclude on some particular pattern of defect. 7. Integration with Scheduled Jobs Regression aspects are covered here. Post unit testing, regression aspects need to be covered and the simplest form is to put them under scheduled execution. This will give a flexibility to run it all the time, be it Sunday or Christmas. 8. Cross-check with UI Testing Report This step is a part of cross-checking database automation testing results to UI testing and can affirm the findings made by two separate channels. Schedule a live demo today! Why Database Automation is Necessary to Solve Common Challenges Frequent Application Releases Data Integrity Tests Checks for Best Practices and Repetitive Database Testing Standards Enforcement Cycles Frequent Changes in Database Uncertainty on Issues Behavior Schema 4 Frequent Application Releases With IT project and product development going agile, testing cycles need to cope up with frequent releases. Since manual testing cannot serve the objective of fast turn-around time signing off the build, automation is must and testing data segment is inevitable. Automating database testing solves challenges of frequent releases and updates. Checks for Best Practices and Standards Enforcement A lot of projects start with really a disciplined development and gets into a spaghetti pattern over a period of time if automated checks are not being kept. The reasons and excuses could be larger teams, scarce time to release, missing code reviews, changing team members and some such. Unless automated watchers are kept, maintenance aspects of the project will suffer. Frequent Changes in Database Schema With ever changing requirements and fast release cycles, it gets really tough to check if an addition of a feature has broken an existing feature or not. Frequent changes in database schema need to be properly tested via automated scripts to avoid any unpleasant surprises. Data Integrity Tests Any inadvertent shifts to data or information as a result of data warehousing, retrieval or action on mission critical data operation, including despiteful attacks, surprising hardware failures and human error is failure of data integrity. Recurring and rigorous continuous tests are required to monitor this aspect. Repetitive Database Testing Cycles For an enterprise application under test, there are multiple vendors contributing to meet the storage requirement of an application. Also, there are multiple layers through which a test needs to pass like Dev, QA, pre-production and production. Performing the same activity repeatedly leads to boredom and inaccuracy. This objective can be achieved with properly drafted automation scripts. Uncertainty on Issues Behavior An issue not getting produced in a staging environment, but is there on production environment and is badly affecting the brand and the revenue of the system. In this case, if automated checks are in place, will definitely allow identifying whether it is the issue with code for latest deployment or whether it is related to data. What Can Be Automated in Database Testing? Data Database Database Database Integrity Health Schema Security Check Check Check Check 5 Data Integrity Check E.g.
Recommended publications
  • Blockchain Database for a Cyber Security Learning System
    Session ETD 475 Blockchain Database for a Cyber Security Learning System Sophia Armstrong Department of Computer Science, College of Engineering and Technology East Carolina University Te-Shun Chou Department of Technology Systems, College of Engineering and Technology East Carolina University John Jones College of Engineering and Technology East Carolina University Abstract Our cyber security learning system involves an interactive environment for students to practice executing different attack and defense techniques relating to cyber security concepts. We intend to use a blockchain database to secure data from this learning system. The data being secured are students’ scores accumulated by successful attacks or defends from the other students’ implementations. As more professionals are departing from traditional relational databases, the enthusiasm around distributed ledger databases is growing, specifically blockchain. With many available platforms applying blockchain structures, it is important to understand how this emerging technology is being used, with the goal of utilizing this technology for our learning system. In order to successfully secure the data and ensure it is tamper resistant, an investigation of blockchain technology use cases must be conducted. In addition, this paper defined the primary characteristics of the emerging distributed ledgers or blockchain technology, to ensure we effectively harness this technology to secure our data. Moreover, we explored using a blockchain database for our data. 1. Introduction New buzz words are constantly surfacing in the ever evolving field of computer science, so it is critical to distinguish the difference between temporary fads and new evolutionary technology. Blockchain is one of the newest and most developmental technologies currently drawing interest.
    [Show full text]
  • An Introduction to Cloud Databases a Guide for Administrators
    Compliments of An Introduction to Cloud Databases A Guide for Administrators Wendy Neu, Vlad Vlasceanu, Andy Oram & Sam Alapati REPORT Break free from old guard databases AWS provides the broadest selection of purpose-built databases allowing you to save, grow, and innovate faster Enterprise scale at 3-5x the performance 14+ database engines 1/10th the cost of vs popular alternatives - more than any other commercial databases provider Learn more: aws.amazon.com/databases An Introduction to Cloud Databases A Guide for Administrators Wendy Neu, Vlad Vlasceanu, Andy Oram, and Sam Alapati Beijing Boston Farnham Sebastopol Tokyo An Introduction to Cloud Databases by Wendy A. Neu, Vlad Vlasceanu, Andy Oram, and Sam Alapati Copyright © 2019 O’Reilly Media Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com). For more infor‐ mation, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Development Editor: Jeff Bleiel Interior Designer: David Futato Acquisitions Editor: Jonathan Hassell Cover Designer: Karen Montgomery Production Editor: Katherine Tozer Illustrator: Rebecca Demarest Copyeditor: Octal Publishing, LLC September 2019: First Edition Revision History for the First Edition 2019-08-19: First Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. An Introduction to Cloud Databases, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the authors, and do not represent the publisher’s views.
    [Show full text]
  • Agile Test Automation Strategy for Anyone and Everyone!
    Agile Test Automation Strategy For Anyone and Everyone! Gerard Meszaros [email protected] Much Ado About Agile 2011 1 Copyright 2011 Gerard Meszaros My Background •Software developer 80’s •Development manager Embedded •Project Manager ----- Telecom •Software architect 90’s •OOA/OOD Mentor •Requirements (Use Case) Mentor ----- I.T. •XP/TDD Mentor •Agile PM Mentor 00’s •Test Automation Consultant & Trainer Gerard Meszaros •Lean/Agile Coach/Consultant [email protected] Product & I.T. Much Ado About Agile 2011 2 Copyright 2011 Gerard Meszaros Agenda • Motivation – The Agile Test Problem – The Fragile Test Problem • Approaches to Test AutomationRough timings for Agile Test Automation Strategy Time per slide: 1.4 # of Slide # • Test Automation Strategy # Topic Time Slides Start End Motivation 11.2 8 2 9 Exercise 1 - Automation Motivation 10 1 10 10 Intro to Automation 7 5 11 15 Exercise 2 - Why not Record & Playback? 10 1 16 16 Why Automated Tests are Fragile 8.4 6 17 22 How Agile Automation Changes Things 9.8 7 24 30 Intro to Example-Driven Development 7 5 32 36 Managing Scope vs Detail in Examples 15.4 11 38 48 How to specify workflows 8.4 6 50 55 Exercise 3 - Workflow Tests (Keyword-Driven) 15 1 56 56 Using Data-Driven Tests to specify business rules 8.4 6 55 60 Exercise 4 - Business Rules Test (Data-Driven) 15 1 61 61 How Tests Interact With the SUT 7 5 62 66 Test-Driven Architecture 5.6 4 67 70 Legacy Systems (if time permits) 19.6 14 71 84 The Role of Unit Tests 8.4 6 85 90 Test Automation Strategy 14 10 91 100 180.2 97 Much
    [Show full text]
  • Middleware-Based Database Replication: the Gaps Between Theory and Practice
    Appears in Proceedings of the ACM SIGMOD Conference, Vancouver, Canada (June 2008) Middleware-based Database Replication: The Gaps Between Theory and Practice Emmanuel Cecchet George Candea Anastasia Ailamaki EPFL EPFL & Aster Data Systems EPFL & Carnegie Mellon University Lausanne, Switzerland Lausanne, Switzerland Lausanne, Switzerland [email protected] [email protected] [email protected] ABSTRACT There exist replication “solutions” for every major DBMS, from Oracle RAC™, Streams™ and DataGuard™ to Slony-I for The need for high availability and performance in data Postgres, MySQL replication and cluster, and everything in- management systems has been fueling a long running interest in between. The naïve observer may conclude that such variety of database replication from both academia and industry. However, replication systems indicates a solved problem; the reality, academic groups often attack replication problems in isolation, however, is the exact opposite. Replication still falls short of overlooking the need for completeness in their solutions, while customer expectations, which explains the continued interest in developing new approaches, resulting in a dazzling variety of commercial teams take a holistic approach that often misses offerings. opportunities for fundamental innovation. This has created over time a gap between academic research and industrial practice. Even the “simple” cases are challenging at large scale. We deployed a replication system for a large travel ticket brokering This paper aims to characterize the gap along three axes: system at a Fortune-500 company faced with a workload where performance, availability, and administration. We build on our 95% of transactions were read-only. Still, the 5% write workload own experience developing and deploying replication systems in resulted in thousands of update requests per second, which commercial and academic settings, as well as on a large body of implied that a system using 2-phase-commit, or any other form of prior related work.
    [Show full text]
  • Test Script Debugger CBTA 3.0 SP11 Document History
    Test Automation - User Guide PUBLIC SAP Solution Manager 7.2 2018-12-03 CBTA - Test Script Debugger CBTA 3.0 SP11 Document History Version Date Change 1.6 2018-12-03 CBTA 3.0 SP11 Update 1.5 2018-05-15 CBTA 3.0 SP10 Update 1.4 2017-09-30 CBTA 3.0 SP9 Update 1.3 2017-03-01 CBTA 3.0 SP8 Update 1.2 2014-05-27 CBTA 3.0 SP2 Update CBTA - Test Script Debugger 2 Document History Table of Contents 1 Running a CBTA Test Script in Debug Mode..........................................................................4 2 How-to start .............................................................................................................................5 2.1 Add or remove breakpoint..................................................................................................................................... 8 2.2 Step Over............................................................................................................................................................ 9 2.3 Run...................................................................................................................................................................... 9 2.4 Stop Debugger................................................................................................................................................... 9 2.5 Error Behavior .......................................................................................................................................................10 2.6 Dynamic Report...............................................................................................................................................
    [Show full text]
  • Database Technology for Bioinformatics from Information Retrieval to Knowledge Systems
    Database Technology for Bioinformatics From Information Retrieval to Knowledge Systems Luis M. Rocha Complex Systems Modeling CCS3 - Modeling, Algorithms, and Informatics Los Alamos National Laboratory, MS B256 Los Alamos, NM 87545 [email protected] or [email protected] 1 Molecular Biology Databases 3 Bibliographic databases On-line journals and bibliographic citations – MEDLINE (1971, www.nlm.nih.gov) 3 Factual databases Repositories of Experimental data associated with published articles and that can be used for computerized analysis – Nucleic acid sequences: GenBank (1982, www.ncbi.nlm.nih.gov), EMBL (1982, www.ebi.ac.uk), DDBJ (1984, www.ddbj.nig.ac.jp) – Amino acid sequences: PIR (1968, www-nbrf.georgetown.edu), PRF (1979, www.prf.op.jp), SWISS-PROT (1986, www.expasy.ch) – 3D molecular structure: PDB (1971, www.rcsb.org), CSD (1965, www.ccdc.cam.ac.uk) Lack standardization of data contents 3 Knowledge Bases Intended for automatic inference rather than simple retrieval – Motif libraries: PROSITE (1988, www.expasy.ch/sprot/prosite.html) – Molecular Classifications: SCOP (1994, www.mrc-lmb.cam.ac.uk) – Biochemical Pathways: KEGG (1995, www.genome.ad.jp/kegg) Difference between knowledge and data (semiosis and syntax)?? 2 Growth of sequence and 3D Structure databases Number of Entries 3 Database Technology and Bioinformatics 3 Databases Computerized collection of data for Information Retrieval Shared by many users Stored records are organized with a predefined set of data items (attributes) Managed by a computer program: the database
    [Show full text]
  • What Is a Database? Differences Between the Internet and Library
    What is a Database? Library databases are mostly full-text material (in their entirety) and summaries or descriptions of articles. They are collections of articles from newspapers, magazines and journals and electronic reference sources. Databases are selected for the quality and variety of resources they offer and are accessed using the Internet. Your library pays for you to have access to a number of relevant databases. You support this with your tuition, so get the most out of your money! You can access them from home or school via the Library Webpage or use the link below. http://www.mxcc.commnet.edu/Content/Find_Articles.asp Two short videos on the benefits of using library databases: http://www.youtube.com/watch?v=VUp1P-ubOIc http://youtu.be/Q2GMtIuaNzU Differences Between the Internet and Library Databases The Internet Library Databases Examples Google, Yahoo, Bing LexisNexis, Literary Reference Center or Health and Wellness Resource Center Review process None – anyone can add Checked for accuracy by content to the Web. publishers. Chosen by your college’s library. Includes “peer-reviewed” scholarly articles. Reliability Unknown Very No quality control mechanisms! Content Anything, from pictures of a Scholarly journal articles, Book person’s pets to personal reviews, Research papers, (usually not researched and Conference papers, and other unsubstantiated) opinions on scholarly information gun control, abortion, etc. How often updated Unknown/varies. Regularly – daily, quarterly monthly Cost “Free” but some of the info Library has paid for you to you may need for your access these databases. assignment requires a fee. Organization Very little or no organization Very organized Availability Websites come and go.
    [Show full text]
  • Data Quality Requirements Analysis and Modeling December 1992 TDQM-92-03 Richard Y
    Published in the Ninth International Conference of Data Engineering Vienna, Austria, April 1993 Data Quality Requirements Analysis and Modeling December 1992 TDQM-92-03 Richard Y. Wang Henry B. Kon Stuart E. Madnick Total Data Quality Management (TDQM) Research Program Room E53-320 Sloan School of Management Massachusetts Institute of Technology Cambridge, MA 02139 USA 617-253-2656 Fax: 617-253-3321 Acknowledgments: Work reported herein has been supported, in part, by MITís Total Data Quality Management (TDQM) Research Program, MITís International Financial Services Research Center (IFSRC), Fujitsu Personal Systems, Inc. and Bull-HN. The authors wish to thank Gretchen Fisher for helping prepare this manuscript. To Appear in the Ninth International Conference on Data Engineering Vienna, Austria April 1993 Data Quality Requirements Analysis and Modeling Richard Y. Wang Henry B. Kon Stuart E. Madnick Sloan School of Management Massachusetts Institute of Technology Cambridge, Mass 02139 [email protected] ABSTRACT Data engineering is the modeling and structuring of data in its design, development and use. An ultimate goal of data engineering is to put quality data in the hands of users. Specifying and ensuring the quality of data, however, is an area in data engineering that has received little attention. In this paper we: (1) establish a set of premises, terms, and definitions for data quality management, and (2) develop a step-by-step methodology for defining and documenting data quality parameters important to users. These quality parameters are used to determine quality indicators, to be tagged to data items, about the data manufacturing process such as data source, creation time, and collection method.
    [Show full text]
  • DBOS: a Proposal for a Data-Centric Operating System
    DBOS: A Proposal for a Data-Centric Operating System The DBOS Committee∗ [email protected] Abstract Current operating systems are complex systems that were designed before today's computing environments. This makes it difficult for them to meet the scalability, heterogeneity, availability, and security challenges in current cloud and parallel computing environments. To address these problems, we propose a radically new OS design based on data-centric architecture: all operating system state should be represented uniformly as database tables, and operations on this state should be made via queries from otherwise stateless tasks. This design makes it easy to scale and evolve the OS without whole-system refactoring, inspect and debug system state, upgrade components without downtime, manage decisions using machine learning, and implement sophisticated security features. We discuss how a database OS (DBOS) can improve the programmability and performance of many of today's most important applications and propose a plan for the development of a DBOS proof of concept. 1 Introduction Current operating systems have evolved over the last forty years into complex overlapping code bases [70,4, 51, 57], which were architected for very different environments than exist today. The cloud has become a preferred platform, for both decision support and online serving applications. Serverless computing supports the concept of elastic provision of resources, which is very attractive in many environments. Machine learning (ML) is causing many applications to be redesigned, and future operating systems must intimately support such applications. Hardware arXiv:2007.11112v1 [cs.OS] 21 Jul 2020 is becoming massively parallel and heterogeneous. These \sea changes" make it imperative to rethink the architecture of system software, which is the topic of this paper.
    [Show full text]
  • Multimedia Database Support for Digital Libraries
    Dagstuhl Seminar 99351 August 29 - September 3 1999 Multimedia Database Support for Digital Libraries E. Bertino (Milano) [email protected] A. Heuer (Rostock) [email protected] T. Ozsu (Alberta) [email protected] G. Saake (Magdeburg) [email protected] Contents 1 Motivation 5 2 Agenda 7 3 Abstracts 11 4 Discussion Group Summaries 24 5 Other Participants 29 4 1 Motivation Digital libraries are a key technology of the coming years allowing the effective use of the Internet for research and personal information. National initiatives for digi- tal libraries have been started in several countries, including the DLI initiative in USA http://www-sal.cs.uiuc.edu/ sharad/cs491/dli.html, Global Info http://www.global- info.org/index.html.en in Germany, and comparable activities in Japan and other Euro- pean countries. A digital library allows the access to huge amounts of documents, where documents themselves have a considerably large size. This requires the use of advanced database technology for building a digital library. Besides text documents, a digital library contains multimedia documents of several kinds, for example audio documents, video sequences, digital maps and animations. All these document classes may have specific retrieval me- thods, storage requirements and Quality of Service parameters for using them in a digital library. The topic of the seminar is the support of such multimedia digital libraries by databa- se technology. This support includes object database technology for managing document structure, imprecise query technologies for example based on fuzzy logic, integration of information retrieval in database management, object-relational databases with multime- dia extensions, meta data management, and distributed storage.
    [Show full text]
  • This Document Explains the Various Benefits That Would Accrue to a User Or Client Who Subscribes to Autorabit
    ® Salesforce Release Automation BENEFITS DOCUMENT This document explains the Various Benefits that would accrue to a user or client who subscribes to AutoRABIT. [email protected] www.autorabit.com Copyright © 2016 AutoRABIT. AutoRABIT Table of Contents About AutoRABIT.............................................................................................................................................................3 AutoRABIT functionality..................................................................................................................................................3 Key Features of AutoRABIT............................................................................................................................................4 Metadata Deployment.....................................................................................................................................................4 Promotion of Builds .........................................................................................................................................................4 Full Deployment..........................................................................................................................................................4 Selective Deployment................................................................................................................................................4 Sandbox Back-up & Restore...........................................................................................................................................5
    [Show full text]
  • Marrying Devops and Test Automation
    ARTICLE Marrying DevOps and Test Automation - a t t e n t i o n. a l w a y s. Is It The Right Thing To Do? Practice Head: Author: Janaki Jayachandran Sharon Paul Independent Testing Services Research Analyst We are all aware of the indifferences among the IT operations and other software development communities that prevail right from the traditional IT era. When developers, operations and testing teams work on different independent silos, focus on individual objectives and performance indicators, they fail to understand the importance of being accountable for any unplanned outages that causes production deployment failure and heavy loss to the company. There had to be a methodology or a practice that facilitated continuous improvement of the delivery cycles by enabling members across the IT and operations feel responsible and accountable for quality of their work. This thought gave rise to the concept of DevOps that fosters cross functional collaboration in order to speed up the delivery cycles through regular customer feedback. How DevOps Culture Impacts Product Quality? DevOps is simply an extension of agile methodology which became quite popular since 2009. It was the solution that resulted due to a series brainstorming sessions by few agile experts who wanted to end the dysfunction in the IT industry. The key reason for the dysfunction was found to be a lack of accountability in terms of quality among the different operations and IT team. Aspire Systems - Marrying DevOps and Test Automation - Is It The Right Thing To Do? 1 Marrying DevOps and Test Automation - Is It The Right Thing To Do? Elisabeth Hendrickson, founder of Quality Tree Software, presented an interesting paper, where she clearly cites a real life scenario of how developers develop a sense of negligence towards quality and they focus more on pushing their features into ‘test’ without taking an effort to evaluate them.
    [Show full text]