Report Entries Sample Clauses

Report Entries. ‌ Running a test sequence or test plan appends the results of each step at the end of test report. Running a test sequence from the beginning (using the Start icon in the Run Toolbar) initializes the test report from the selected template file then adds the test sequence Objective and Preferences. This creates a clean report each time the test sequence is run. Running a test sequence using the other controls does not clear the test report or add the Objective or Preferences, making it easier to troubleshoot (single step etc.) a test. After each step runs, the information about that step is appended to the test report as shown below. This information includes the Title, Value, Comment, Result and Data of each step. Title includes the enable checkbox, step number, icon, type and test sequence file name. Value and Comment are the test sequence information from the Step Value/Comment tab (design window). Result shows the result icon, title, date/time the step completed and the elapsed time the step completed from the beginning of the test. Note that not all steps produce data. The data also includes any errors that occurred running the step. Result and Data are also shown in the Step Result tab in the test sequence window .
AutoNDA by SimpleDocs

Related to Report Entries

  • Monthly Progress Reports During the Construction Period, the Concessionaire shall, no later than 7 (seven) days after the close of each month, furnish to the Authority and the Independent Engineer a monthly report on progress of the Construction Works and shall promptly give such other relevant information as may be required by the Independent Engineer.

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.

  • Quarterly Progress Reports The goal of this task is to periodically verify that satisfactory and continued progress is made towards achieving the objectives of this Agreement on time and within budget. The objectives of this task are to summarize activities performed during the reporting period, to identify activities planned for the next reporting period, to identify issues that may affect performance and expenditures, and to form the basis for determining whether invoices are consistent with work performed. The Recipient shall: • Prepare a Quarterly Progress Report which summarizes all Agreement activities conducted by the Recipient for the reporting period, including an assessment of the ability to complete the Agreement within the current budget and any anticipated cost overruns. Progress reports are due to the CAM the 10th day of each January, April, July, and October. The Quarterly Progress Report template can be found on the ECAMS Resources webpage available at xxxxx://xxx.xxxxxx.xx.xxx/media/4691. Product: • Quarterly Progress Reports

  • Progress Reports The Recipient shall submit to the OPWC, at the OPWC's request, summary reports detailing the progress of the Project pursuant to this Agreement and any additional reports containing such information as the OPWC may reasonably require.

  • Monthly Progress Report ‌ 2 Developer shall provide additional, separate, filtered reports of the Project activities and Work 3 elements based on the Monthly Progress Schedule with the Monthly Progress Report, including 4 the following:

  • Progress Report 10.1 If required, you shall submit progress reports in connection with the Service (“Report”) on at least a monthly basis, or as we may require. The Report shall include a summary of the activities and accomplishments during the previous reporting period.

Time is Money Join Law Insider Premium to draft better contracts faster.