scholarly journals Automated Testing of Timeliness : A Case Study

Author(s):  
Robert Nilsson ◽  
Jeff Offutt
Keyword(s):  
2021 ◽  
Author(s):  
◽  
Dayu Guan

<p>Purpose - The purpose of this case study is to understand how two organizations view and utilise automated testing and how it relates to the literature. It outlines and discusses the key factors to be taken into consideration when setting up an automated testing, in addition to the risks involved.  Design/methodology/approach – Focus group discussions were executed to collect the data and the findings were compared with other literatures.  Findings – For cognition of automated testing, it is not only limited to its definition and benefits that may be brought into the organization, but also need to focus more on scope of application and preconditions. Aside from the key considerations such as people resistance, working process and training, some other concerns were also found from managerial perspective when adopting automated testing: (1) Cost-benefit – Return of Investment (ROI) is an effective method to analyse the investment, especially for the factors affecting the cost of investment; (2) Management support. It includes balancing between business and technology, management involvement and coordinating the relations between the departments; (3) Tool selection: Choosing the right automation tool is a very complicated process with a lot internal factors involved.  Practical implication – For an organization that doesn’t have automated testing implemented yet, a pilot project can be the first option to understand its practicality and applicability based on individual organizational context.  Originality/Value – This case study can be used for an organization that interests in better introducing and implementing automated testing within the organization.  Key Words – Automated testing, Cost-benefit, Management support, Tool selection, practicality, applicability and ROI.  Paper Type – Case Study Research.</p>


2020 ◽  
Vol 20 (3) ◽  
pp. 39-47
Author(s):  
Matej MADEJA ◽  
◽  
Jaroslav PORUBAN ◽  
Veljko PEJOVIC ◽  
Martin GJORESKI ◽  
...  

Author(s):  
Hareton Leung ◽  
Keith Chan

This case study describes experience of an IT organization in implementing automated testing of their management information system. The goal of the project and project plan are presented first. The needs and benefits of automated testing, and problems and challenges related to adoption of software tools are identified.


2021 ◽  
Author(s):  
◽  
Dayu Guan

<p>Purpose - The purpose of this case study is to understand how two organizations view and utilise automated testing and how it relates to the literature. It outlines and discusses the key factors to be taken into consideration when setting up an automated testing, in addition to the risks involved.  Design/methodology/approach – Focus group discussions were executed to collect the data and the findings were compared with other literatures.  Findings – For cognition of automated testing, it is not only limited to its definition and benefits that may be brought into the organization, but also need to focus more on scope of application and preconditions. Aside from the key considerations such as people resistance, working process and training, some other concerns were also found from managerial perspective when adopting automated testing: (1) Cost-benefit – Return of Investment (ROI) is an effective method to analyse the investment, especially for the factors affecting the cost of investment; (2) Management support. It includes balancing between business and technology, management involvement and coordinating the relations between the departments; (3) Tool selection: Choosing the right automation tool is a very complicated process with a lot internal factors involved.  Practical implication – For an organization that doesn’t have automated testing implemented yet, a pilot project can be the first option to understand its practicality and applicability based on individual organizational context.  Originality/Value – This case study can be used for an organization that interests in better introducing and implementing automated testing within the organization.  Key Words – Automated testing, Cost-benefit, Management support, Tool selection, practicality, applicability and ROI.  Paper Type – Case Study Research.</p>


Author(s):  
D. Boyne ◽  
J. Goertz ◽  
D. Parsons

Abstract Failure analysis of non-volatile memory arrays can be complicated by the history of bits elsewhere in the array. This generally is in contrast to volatile memories, in which the state of all bits can quickly be reset by over-writing the bits, or by simply removing power from the array. On one of our products, EEPROM bits failed to program if certain patterns of bits were programmed elsewhere in the EEPROM array. During programming, high voltages (&gt;18 volts) are present within the EEPROM array. Such voltage levels caused a narrow field oxide region to break down, thereby pulling down the programming voltage and preventing the successful programming of EEPROM transistors. What complicated the analysis, however, was that the breakdown only occurs if a checkerboard pattern is being programmed in one part of the array, while specific other EEPROM bits had previously been programmed elsewhere in the array. Until the failure mechanism was well understood, electrical screens were difficult to implement, because they typically do not account for complicated interactions between bits. This is especially true for nonvolatile memories, for which test time costs often prohibit the use of complicated test patterns with improved test coverage. This paper reviews the failure analysis, and proceeds to highlight the importance of knowing the contents of nonvolatile arrays prior to performing either failure analysis or automated testing on such an array. The case study therefore applies to both test and failure analysis engineers.


Sign in / Sign up

Export Citation Format

Share Document