Spider Testing Conclusions Sample Clauses

Spider Testing Conclusions. Both types of tests have given valuable input to the developers. Some programming was needed for the technical test to read log of performance. However, we are now able to run tests going forward and with some planed for improvements we hope to run additional technical spider tests within the project. To summarise the user reports, we highlight that all users were given one hour only for the actual testing. The major outcomes are as follows: • Some minor delays were reported from one tester while the rest fulfilled the test in approximately 60 minutes. • Managing a spider without any training is challenging. However, out of the 5 user only one failed in managing the spider based upon the quick guide and a 2min 35sec video with no sound. • Inserting 10 blogs each, proved close to 90% success rate excluding non-existing blog sites. This is according to the internal, technical and scaled test as well. • In 20 minutes 180-190 blogs and 10-35 comments was captured, which indicates in average 6 seconds per captured post/comment. • There is a CSV issue with automated numbering of the inserted blog URL into the default CSV file. This feedback is put on the bug list. • Feature testing: most features were found and accepted by all testers. Also some testers had difficulties finding the features in the spider portal. No documented missing features. Overall impression: Strengths: speed and user-friendliness. State of the art: requires no training, efficient and does not need manual work.
Sample 1
AutoNDA by SimpleDocs

Related to Spider Testing Conclusions

  • Meter Testing Company shall provide at least twenty-four (24) hours' notice to Seller prior to any test it may perform on the revenue meters or metering equipment. Seller shall have the right to have a representative present during each such test. Seller may request, and Company shall perform, if requested, tests in addition to the every fifth-year test and Seller shall pay the cost of such tests. Company may, in its sole discretion, perform tests in addition to the fifth year test and Company shall pay the cost of such tests. If any of the revenue meters or metering equipment is found to be inaccurate at any time, as determined by testing in accordance with this Section 10.2 (Meter Testing), Company shall promptly cause such equipment to be made accurate, and the period of inaccuracy, as well as an estimate for correct meter readings, shall be determined in accordance with Section 10.3 (Corrections).

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Follow-up Testing An employee shall submit to unscheduled follow-up drug and/or alcohol testing if, within the previous 24-month period, the employee voluntarily disclosed drug or alcohol problems, entered into or completed a rehabilitation program for drug or alcohol abuse, failed or refused a preappointment drug test, or was disciplined for violating the provisions of this Agreement and Employer work rules. The Employer may require an employee who is subject to follow-up testing to submit to no more than six unscheduled drug or alcohol tests within any 12 month period.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Substance Abuse Testing The Parties agree that it is in the best interest of all concerned to promote a safe working environment. The Union has no objection to pre-employment substance abuse testing when required by the Employer and further, the Union has no objection to voluntary substance abuse testing to qualify for employment on projects when required by a project owner. The cost and scheduling of such testing shall be paid for and arranged by the Employer. The Union agrees to reimburse the Employer for any failed pre-access Alcohol and Drug test costs.

  • Repair Testing At the time of repair of a LIS trunk group, at no additional charge, tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act.

  • Alcohol Testing Alcohol testing will be conducted by using an evidential breath testing device (EBT) approved by the National Highway Traffic Safety Administration. Non-EBT devices may be used for initial screening tests. A screening test will be conducted first. If the result is an alcohol concentration level of less than 0.02, the test is considered a negative test. If the alcohol concentration level is 0.02 or more, a second confirmation test will be conducted. Levels of .04 or greater on the confirmation test will be considered positive.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

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