mox | 易学教程

测试成本--半导体测试最大的障碍

阅读更多关于测试成本--半导体测试最大的障碍

前言半导体测试产品提供商面临的一些最大挑战已经存在数十年了：测试成本，提高测试程序的质量以及不妨碍设计人员的生产率，这些仍将是需要克服的主要障碍。如今，随着越来越复杂的设备的出现，测试设备提供商需要不断创新并满足当今快速发展的需求。半导体测试领域还面临着其他挑战。移动电子推动了对更小的半导体节点的需求，而其他现代因素（例如云利用率，人工智能和5G）都给测试人员带来了自身的困难。半导体测试的挑战有机构对几家领先的半导体测试供应商进行了调查，了解他们认为这一领域最大的挑战是什么，以及他们的公司正在做什么来克服这些挑战。他们这样说： Advantest营销传播副总裁judydavies： “移动电子产品需求的激增，推动了向小型半导体产品方向发展的趋势。7纳米及更小的设计节点是目前发展的趋势。结果，芯片的工作电压继续下降。因此，精度要求变得至关重要，而参数测试现在要求直流精度在毫伏范围内。与此同时，云计算、大数据和人工智能（AI）也在不断增加对服务器和数据中心的需求，这些都需要高带宽和高密度的存储设备。我们预计，随着数字转型的推进，对海量数据存储、计算能力增强和高速通信的需求将继续增长。因此，客户对小型节能集成电路的需求越来越高，半导体的可靠性也越来越受到重视。这提高了测试标准，为测试仪市场带来了新的挑战和机遇。在高性能计算领域，我们正在使用微处理器

How do I mock a class property with mox?

阅读更多关于 How do I mock a class property with mox?

问题 I have a class: class MyClass(object): @property def myproperty(self): return 'hello' Using mox and py.test , how do I mock out myproperty ? I've tried: mock.StubOutWithMock(myclass, 'myproperty') myclass.myproperty = 'goodbye' and mock.StubOutWithMock(myclass, 'myproperty') myclass.myproperty.AndReturns('goodbye') but both fail with AttributeError: can't set attribute . 回答1: When stubbing out class attributes mox uses setattr . Thus mock.StubOutWithMock(myinstance, 'myproperty') myinstance

Python SQLAlchemy - Mocking a model attribute's “desc” method

阅读更多关于 Python SQLAlchemy - Mocking a model attribute's “desc” method

问题 In my application, there is a class for each model that holds commonly used queries (I guess it's somewhat of a "Repository" in DDD language). Each of these classes is passed the SQLAlchemy session object to create queries with upon construction. I'm having a little difficulty in figuring the best way to assert certain queries are being run in my unit tests. Using the ubiquitous blog example, let's say I have a "Post" model with columns and attributes "date" and "content". I also have a

Python SQLAlchemy - Mocking a model attribute's “desc” method

阅读更多关于 Python SQLAlchemy - Mocking a model attribute's “desc” method

In my application, there is a class for each model that holds commonly used queries (I guess it's somewhat of a "Repository" in DDD language). Each of these classes is passed the SQLAlchemy session object to create queries with upon construction. I'm having a little difficulty in figuring the best way to assert certain queries are being run in my unit tests. Using the ubiquitous blog example, let's say I have a "Post" model with columns and attributes "date" and "content". I also have a "PostRepository" with the method "find_latest" that is supposed to query for all posts in descending order

Mocking open(file_name) in unit tests

阅读更多关于 Mocking open(file_name) in unit tests

问题 I have a source code that opens a csv file and sets up a header to value association. The source code is given below: def ParseCsvFile(source): """Parse the csv file. Args: source: file to be parsed Returns: the list of dictionary entities; each dictionary contains attribute to value mapping or its equivalent. """ global rack_file rack_type_file = None try: rack_file = source rack_type_file = open(rack_file) # Need to mock this line. headers = rack_type_file.readline().split(',') length = len