Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| summerofcode2017:smoketestingofbaseutilities [2017/07/09 17:39] – Add progress report for week 5 ; Update differential status ShivanshRai | summerofcode2017:smoketestingofbaseutilities [2021/04/26 04:41] (current) – Fix MailTo macros. JethroNederhof | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ====== Overview ====== | ====== Overview ====== | ||
| Smoke testing is a set of light tests which are done for checking basic functionalities of a software to ascertain if the crucial functions work correctly.\\ | Smoke testing is a set of light tests which are done for checking basic functionalities of a software to ascertain if the crucial functions work correctly.\\ | ||
| - | %%FreeBSD%% currently has a set of [[https:// | + | %%FreeBSD%% currently has a set of [[/ |
| ====== Project Description ====== | ====== Project Description ====== | ||
| Line 26: | Line 26: | ||
| * Study the current problems faced as a developer or tester when writing new test cases, and the problems faced as a release engineer or tester when executing existing test cases. | * Study the current problems faced as a developer or tester when writing new test cases, and the problems faced as a release engineer or tester when executing existing test cases. | ||
| - | ===== Test Plan ===== | + | \\ |
| + | ====== Initially Proposed Test Plan ====== | ||
| The file [[https:// | The file [[https:// | ||
| - | |||
| - | The smoke tests can be run using the following commands - | ||
| - | |||
| - | < | ||
| - | >> make | ||
| - | >> make test | ||
| - | </ | ||
| It should be noted that finally the tests will be automated with appropriately passed options. The above commands will not have to be run for testing individual programs. | It should be noted that finally the tests will be automated with appropriately passed options. The above commands will not have to be run for testing individual programs. | ||
| Line 48: | Line 42: | ||
| An automation script will be written which will populate '' | An automation script will be written which will populate '' | ||
| The initial version of the generated test scripts will only test trivial functionalities.\\ | The initial version of the generated test scripts will only test trivial functionalities.\\ | ||
| - | |||
| - | | ★ More details regarding automated generation of test scripts available [[https:// | ||
| Although the test plan does not check the entire state of application under test, it suffices for the initial purposes of smoke testing. | Although the test plan does not check the entire state of application under test, it suffices for the initial purposes of smoke testing. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | <callout type=" | ||
| + | **Revised test plan** | ||
| + | |||
| + | The test plan for the project has been completely revamped (a brief overview available [[https:// | ||
| + | </ | ||
| + | |||
| + | \\ | ||
| ====== Expected Results ====== | ====== Expected Results ====== | ||
| - | * Set of test programs | + | * An automated tooling |
| - | * An automated tooling | + | * Set of test programs generated by the tool to verify basic functionality |
| - | (To be updated) | + | |
| ====== Milestones ====== | ====== Milestones ====== | ||
| Line 64: | Line 65: | ||
| | **Start of Coding** | | **Start of Coding** | ||
| | 1 | May 30 | Start of coding. | ✔ | | | 1 | May 30 | Start of coding. | ✔ | | ||
| - | | **Add kyua based tests** | + | | **Add atf-sh |
| - | | 1 | May 30 - June 5 | Start adding | + | | 1 | May 30 - June 5 | Start adding |
| | 2 | June 6 - June 12 | ::: | ::: | | | 2 | June 6 - June 12 | ::: | ::: | | ||
| - | | 3 | June 13 - June 19 | [[https:// | + | | 3 | June 13 - June 19 | [[https:// |
| - | | ::: | ::: | Fix a bug in the implementation of ln(1). | ::: | | + | | ::: | ::: | Fix a bug in the implementation of ln(1). |
| - | | 4 | June 20 - June 26 | Add functionality to generate trivial tests. | ✔ | | + | | 4 | June 20 - June 26 | Add functionality to generate trivial tests. |
| | **First evaluations** | | **First evaluations** | ||
| + | | **Start generating testcases to demonstrate tool behavior in different cases.** | ||
| + | | 5 | June 27 - July 3 | Demonstrate negative testcases for ln(1). [[https:// | ||
| + | | ::: | ::: | Support for utilities with no supported options. | ||
| + | | ::: | ::: | Collation of common usage message. | ||
| + | | 6 | July 4 - July 10 | Demonstrate the tests which the tool can generate using date(1), ln(1) and stdbuf(1). [[https:// | ||
| + | | 7 | June 11 - July 17 | Add functionality for reading annotations. [[https:// | ||
| + | | **Second evaluations** | ||
| + | | **Bug fixes and code cleanup** | ||
| + | | 8 | June 18 - July 24 | Add functionality of dynamically generating annotations. [[https:// | ||
| + | | 9 | June 25 - Aug 1 | Miscellaneous fixes. [[https:// | ||
| + | | 10 | Aug 2 - Aug 8 | Updates to scripts. [[https:// | ||
| + | | 11 | Aug 9 - Aug 15 | ::: | ::: | | ||
| + | | 12 | Aug 16 - Aug 22 | Add functionality to stop test generation during runtime. [[https:// | ||
| + | | 13 | Aug 23 - Aug 29 | ::: | ::: | | ||
| + | | **Update documentation** | ||
| + | | **Final evaluations** | ||
| - | Table design adapted from [[https:// | + | Table design adapted from [[SummerOfCode2016/ |
| ====== Deliverables ====== | ====== Deliverables ====== | ||
| ===== Deliverables for first evaluation ===== | ===== Deliverables for first evaluation ===== | ||
| - | * Add '' | + | * Add atf-sh |
| * Prepare a basic design of the automation tool. Cover generation of a limited number of test scripts. | * Prepare a basic design of the automation tool. Cover generation of a limited number of test scripts. | ||
| - | (To be updated) | + | |
| + | ===== Deliverables for second evaluation ===== | ||
| + | * Add functionality to enable users in defining which testcases to ignore while generating tests. | ||
| + | |||
| + | * Generate tests for all section 1 utilities and try to identify [[https:// | ||
| + | |||
| + | ===== Deliverables for third evaluation ===== | ||
| + | * Finish adding functionality to halt test generation during runtime. | ||
| + | |||
| + | * Clean up the code and prepare it for merge into the src tree. | ||
| + | |||
| + | * Add a [[https:// | ||
| ====== Weekly Reports ====== | ====== Weekly Reports ====== | ||
| + | **Note:** While visiting links in the following reports to **// | ||
| ^ Week ^ Report | ^ Week ^ Report | ||
| Line 89: | Line 118: | ||
| | 4 | [[https:// | | 4 | [[https:// | ||
| | 5 | [[https:// | | 5 | [[https:// | ||
| + | | 6 | [[https:// | ||
| + | | 7 | [[https:// | ||
| + | | 8 | [[https:// | ||
| + | | The test generation tool was ready at this point || | ||
| + | | 12 | [[https:// | ||
| ====== Bugs reported ====== | ====== Bugs reported ====== | ||
| Line 96: | Line 130: | ||
| ====== The Code ====== | ====== The Code ====== | ||
| - | [[https:// | ||
| - | ===== Differentials ===== | + | <callout type=" |
| + | [[https:// | ||
| + | |||
| + | Contains the implementation of test generation tool. Also contains the implementation of the initially-proposed test plan. | ||
| + | |||
| + | [[https:// | ||
| + | </ | ||
| + | |||
| + | ===== Differentials | ||
| ^ Week ^ Differential | ^ Week ^ Differential | ||
| Line 107: | Line 148: | ||
| | 3 | [[https:// | | 3 | [[https:// | ||
| | ::: | [[https:// | | ::: | [[https:// | ||
| - | | 4 | [[https:// | + | | 4 | [[https:// |
| - | | ::: | [[https:// | + | | ::: | [[https:// |
| | 5 | [[https:// | | 5 | [[https:// | ||
| + | | 10 | [[https:// | ||
| + | | The differential submitted on week 10 lays the basic structure of the generated tests ||| | ||
| + | | 12 | [[https:// | ||
| ---- | ---- | ||