Best Python code snippet using tempest_python
upload_archive.py
Source: upload_archive.py
...22# language governing permissions and limitations under the License.23import logging24import boto325from botocore.exceptions import ClientError26def upload_archive(vault_name, src_data):27 """Add an archive to an Amazon S3 Glacier vault.28 The upload occurs synchronously.29 :param vault_name: string30 :param src_data: bytes of data or string reference to file spec31 :return: If src_data was added to vault, return dict of archive32 information, otherwise None33 """34 # The src_data argument must be of type bytes or string35 # Construct body= parameter36 if isinstance(src_data, bytes):37 object_data = src_data38 elif isinstance(src_data, str):39 try:40 object_data = open(src_data, 'rb')41 # possible FileNotFoundError/IOError exception42 except Exception as e:43 logging.error(e)44 return None45 else:46 logging.error('Type of ' + str(type(src_data)) +47 ' for the argument \'src_data\' is not supported.')48 return None49 glacier = boto3.client('glacier')50 try:51 archive = glacier.upload_archive(vaultName=vault_name,52 body=object_data)53 except ClientError as e:54 logging.error(e)55 return None56 finally:57 if isinstance(src_data, str):58 object_data.close()59 # Return dictionary of archive information60 return archive61def main():62 """Exercise upload_archive()"""63 # Assign these values before running the program64 test_vault_name = 'VAULT_NAME'65 filename = 'C:\\path\\to\\filename.ext'66 # Alternatively, specify object contents using bytes.67 # filename = b'This is the data to store in the Glacier archive.'68 # Set up logging69 logging.basicConfig(level=logging.DEBUG,70 format='%(levelname)s: %(asctime)s: %(message)s')71 # Upload the archive72 archive = upload_archive(test_vault_name, filename)73 if archive is not None:74 logging.info(f'Archive {archive["archiveId"]} added to {test_vault_name}')75if __name__ == '__main__':...
Check out the latest blogs from LambdaTest on this topic:
These days, development teams depend heavily on feedback from automated tests to evaluate the quality of the system they are working on.
I think that probably most development teams describe themselves as being “agile” and probably most development teams have standups, and meetings called retrospectives.There is also a lot of discussion about “agile”, much written about “agile”, and there are many presentations about “agile”. A question that is often asked is what comes after “agile”? Many testers work in “agile” teams so this question matters to us.
I routinely come across test strategy documents when working with customers. They are lengthy—100 pages or more—and packed with monotonous text that is routinely reused from one project to another. Yawn once more— the test halt and resume circumstances, the defect management procedure, entrance and exit criteria, unnecessary generic risks, and in fact, one often-used model replicates the requirements of textbook testing, from stress to systems integration.
To understand the agile testing mindset, we first need to determine what makes a team “agile.” To me, an agile team continually focuses on becoming self-organized and cross-functional to be able to complete any challenge they may face during a project.
When working on web automation with Selenium, I encountered scenarios where I needed to refresh pages from time to time. When does this happen? One scenario is that I needed to refresh the page to check that the data I expected to see was still available even after refreshing. Another possibility is to clear form data without going through each input individually.
Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.
You could also refer to video tutorials over LambdaTest YouTube channel to get step by step demonstration from industry experts.
Get 100 minutes of automation test minutes FREE!!