登录查看更多内容

Last updated on 2024年7月1日

How do you update and maintain your smoke test suite as the functional requirements change?

由人工智能和领英社区提供技术支持

Smoke testing is a type of functional testing that verifies the basic functionality and stability of a software system before performing more detailed tests. It helps you identify any major defects or issues that could prevent further testing or deployment. However, as the functional requirements of your system change over time, you need to update and maintain your smoke test suite accordingly. In this article, you will learn how to do that effectively and efficiently.

此文章中的业界达人

由社区从 6 条内容中精选。了解更多

Ashok Kumar

Engineering Leader |Software Testing Top Voice| Agile Evangelist | Speaker | Mentor
Ashwin Sathyanarayanan

Testing | QA | Automation Testing| Framework Development| Selenium| WebDriverIO | RestAssured | Postman | Appium
Zouhair B.

Ingénieur Test Fonctionnel et Automatisé Confirmé | Consultant et Formateur Selenium | ISTQB? CTFL - Scrum | A4Q?…

1 Review the functional requirements

The first step to update and maintain your smoke test suite is to review the functional requirements of your system regularly. You need to understand what are the core features and functionalities that your system should deliver, and how they are affected by any changes or updates. You should also check the priority and risk level of each requirement, and align them with the expectations and needs of your stakeholders and users.

添加您的观点

Zouhair B.

Ingénieur Test Fonctionnel et Automatisé Confirmé | Consultant et Formateur Selenium | ISTQB? CTFL - Scrum | A4Q? Selenium Tester Certified
举报内容
Pour maintenir et mettre à jour notre suite de tests de fumée au fur et à mesure que les exigences fonctionnelles évoluent, nous suivons un processus agile et itératif. Tout d'abord, nous surveillons attentivement les changements dans les exigences fonctionnelles et les fonctionnalités du logiciel. Ensuite, nous identifions les impacts potentiels sur nos tests de fumée existants et évaluons si de nouveaux cas de test doivent être ajoutés, ou si des tests existants doivent être modifiés ou supprimés. Nous accordons une priorité particulière aux fonctionnalités critiques et aux scénarios d'utilisation principaux pour assurer une couverture adéquate.

已翻译

赞
Kaushik Maitra CSM?

Technical Consultant in TCS BENGALURU|| ??Certified ScrumMaster? ||??36K LinkedIn Family.|| Web Accessibility Test Lead ||Automation Tester|| PMO Operations||
举报内容
Functional requirements are statements that define what a system or product must or must not do to meet user needs. They are usually expressed as "if a given condition holds, then the system should respond appropriately". Functional requirements can be mandatory and must be met by the product unless the requirement is changed

已翻译

赞

2 Identify the smoke test cases

The next step is to identify the smoke test cases that cover the essential functionality and stability of your system. These are the test cases that you will run every time you have a new build or version of your system, to ensure that it is ready for further testing or deployment. When selecting the smoke test cases, they should be simple, fast, and easy to execute and automate, as well as cover the main scenarios and workflows of your system. Additionally, they should verify the integration and communication of your system with other systems or components, such as databases, APIs, or third-party services. Finally, they should detect any major defects or issues that could compromise the quality or performance of your system, such as crashes, errors, or data loss.

添加您的观点

Ashwin Sathyanarayanan

Testing | QA | Automation Testing| Framework Development| Selenium| WebDriverIO | RestAssured | Postman | Appium
举报内容
In smoke tests, the number of automation test cases should be very minimal and it should touch all the critical endpoints and see if there are connectivity issues, page loads are successful and verify application does not have any major issues.

已翻译

赞
Ashok Kumar

Engineering Leader |Software Testing Top Voice| Agile Evangelist | Speaker | Mentor
举报内容
Identify nuclear checks that can be quickly executed on a CI pipeline. Quick feedback is key to selecting tests for smoke automation. The bigger the check is the bulkier would be the overall smoke schedule. While increasing the coverage of smoke testing is important, it is equally important to monitor the time taken to complete the smoke schedule. A benchmark for the overall time taken for the smoke schedule to be completed must be defined and the daily run must be measured against this benchmark. The tests are then fine-tuned and trimmed down to meet the benchmark SLA.

已翻译

赞

3 Update and optimize the smoke test cases

The third step is to update and optimize the smoke test cases according to the changes or updates in the functional requirements. To do this, you should add new smoke test cases for any new or modified features or functionalities that are essential or high-priority for your system. Additionally, you should review and remove or modify any smoke test cases that are obsolete, redundant, or irrelevant for your system, or that are covered by other test cases. Moreover, you should review and improve the design, structure, and logic of your smoke test cases to make them clearer, more concise, and consistent. Furthermore, you should use test data and parameters that are realistic, valid, and representative of your system's behavior and environment. Finally, it's beneficial to implement test automation tools and frameworks that can help you execute and maintain your smoke test cases faster and easier.

添加您的观点

Talib Usmani ????

Senior SQA Engineer || Manual and Automation || Backend QA || Scrum Master || Top Voice || Google Certified Project Manager || Blockchain QA || Fintech QA
举报内容
The systematic way (Process) to update and optimize the smoke test cases are: - Review the current smoke test suite. - Identify High Priority and Critical areas that have not been added to the test suite. - Analyze new features added and high-priority bug fixes and cover the test cases left from those. - Include edge cases in the smoke test cases. By following all these steps you can easily update and optimize the smoke test cases and ensure maximum test coverage of app.

已翻译

赞

4 Document and communicate the smoke test suite

The fourth step is to document and communicate the smoke test suite to your team and stakeholders. A test plan should be created and maintained to outline the scope, objectives, and strategy of the smoke test suite, as well as the roles, responsibilities, and resources involved. A test management tool or system can help organize, track, and report smoke test cases, results, and defects. Additionally, a naming convention and format should be used to identify and categorize smoke test cases easily and accurately. Comments and annotations should be added to explain the purpose, steps, and expected outcomes of smoke test cases, as well as any assumptions, dependencies or limitations. Furthermore, it is important to share and review the smoke test suite with your team and stakeholders regularly in order to receive their feedback and suggestions.

添加您的观点

5 Execute and monitor the smoke test suite

Executing and monitoring the smoke test suite is the fifth step, which should be done whenever a new build or version of the system is available, or before any major testing or deployment activity. To do this, you must run the smoke test suite on an environment that closely resembles production. Additionally, a test automation tool or framework should be used to run the suite quickly and reliably, and to generate and store test results and logs. After analyzing and evaluating the results, any defects or issues should be reported and communicated to team members and stakeholders, who will then prioritize and assign them accordingly. Finally, the smoke test suite should be updated and maintained based on the test results and defects, as well as any changes in functional requirements.

添加您的观点

Ashok Kumar

Engineering Leader |Software Testing Top Voice| Agile Evangelist | Speaker | Mentor
举报内容
Monitoring the infrastructure prerequisites is also key to establishing an effective smoke test pipeline. The nodes that are used to run smoke tests need to be monitored for their health as well and this needs to be a prerequisite check that runs before the actual smoke test jobs are executed.

已翻译

赞

6 Review and improve the smoke test suite

The sixth and final step is to review and improve the smoke test suite periodically, to ensure that it is effective and efficient. You should measure and monitor the quality and performance of your smoke test suite, using metrics such as coverage, execution time, defect rate, pass rate, and automation rate. If any defects or issues were missed or introduced by your smoke test suite, you should conduct a root cause analysis and identify any gaps or weaknesses in your smoke test strategy or execution. Additionally, you should implement corrective and preventive actions to address any problems or risks in your smoke test suite. Finally, have a retrospective or lesson learned session with your team and stakeholders to review feedback and suggestions for your smoke test suite and identify best practices or improvement opportunities.

添加您的观点

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Functional Testing

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you update and maintain your smoke test suite as the functional requirements change?

1

2

3

4

5

6

7

1 Review the functional requirements

2 Identify the smoke test cases

3 Update and optimize the smoke test cases

4 Document and communicate the smoke test suite

5 Execute and monitor the smoke test suite

6 Review and improve the smoke test suite

7 Here’s what else to consider

Functional Testing

给文章评分

感谢您的反馈

更多Functional Testing相关文章

更多相关阅读内容