Software Testing Principles Followed Sample Clauses

Software Testing Principles Followed. During the last 40 years, several principles for testing have become accepted as general rules for test work [11]. For the purpose of D5.2 we have followed the following principles: ✓ Principle - Testing shows the presence of defects, not their absence: Testing can show that there are defects. Testing cannot prove that the BlogForever platform is defect-free. Even if no failures are found during testing, this is no proof that there are no defects. ✓ Principle - Exhaustive testing is not possible: Every test is always just a sample. The test effort is therefore controlled, taking into account risk and priorities. ✓ Principle - Testing activities should start as early as possible: Testing activities should start as early as possible in the software lifecycle and should focus on defined goals. This contributes to finding defects early. ✓ Principle - Test is context dependent: Testing must be adapted to the risks inherent in the use and environment of the platform tested. Therefore, no two platforms should be tested in the exactly same way. ✓ Principle - The fallacy of assuming that no failures mean a useful system Finding failures and repairing defects does not guarantee that the system as a whole meets user expectations and needs. Early involvement of the users in the development process and the use of prototypes are preventive measures intended to avoid problems. The BlogForever platform development is agile, which means the development follows continuous delivery of valuable software, updating working software frequently. Developments for the platform are done incrementally and iteratively, building up each feature to improve the overall outcome. The BlogForever platform testing processes are a fundamental part of the overall incremental and iterative workflow. They assess and feedback relevant information to the development cycles. Ultimately all the testing processes applied within T5.2 were as objective as possible trying to find issues that will limit the success of the BlogForever platform in the long run. They were intended to test the BlogForever platform extensively; generate feedback from users; and minimise system problems. The purpose of this testing is quality assurance, verification and validation.
Sample 1
AutoNDA by SimpleDocs

Related to Software Testing Principles Followed

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • 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.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Accounting Methods and Financial Records Maintain a system of accounting, and keep such books, records and accounts (which shall be true and complete in all material respects) as may be required or as may be necessary to permit the preparation of financial statements in accordance with GAAP and in compliance with the regulations of any Governmental Authority having jurisdiction over it or any of its properties.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Long Term Cost Evaluation Criterion # 4 READ CAREFULLY and see in the RFP document under "Proposal Scoring and Evaluation". Points will be assigned to this criterion based on your answer to this Attribute. Points are awarded if you agree not i ncrease your catalog prices (as defined herein) more than X% annually over the previous year for years two and thr ee and potentially year four, unless an exigent circumstance exists in the marketplace and the excess price increase which exceeds X% annually is supported by documentation provided by you and your suppliers and shared with TIP S, if requested. If you agree NOT to increase prices more than 5%, except when justified by supporting documentati on, you are awarded 10 points; if 6% to 14%, except when justified by supporting documentation, you receive 1 to 9 points incrementally. Price increases 14% or greater, except when justified by supporting documentation, receive 0 points. increases will be 5% or less annually per question Required Confidentiality Claim Form This completed form is required by TIPS. By submitting a response to this solicitation you agree to download from th e “Attachments” section, complete according to the instructions on the form, then uploading the completed form, wit h any confidential attachments, if applicable, to the “Response Attachments” section titled “Confidentiality Form” in order to provide to TIPS the completed form titled, “CONFIDENTIALITY CLAIM FORM”. By completing this process, you provide us with the information we require to comply with the open record laws of the State of Texas as they ma y apply to your proposal submission. If you do not provide the form with your proposal, an award will not be made if your proposal is qualified for an award, until TIPS has an accurate, completed form from you. Read the form carefully before completing and if you have any questions, email Xxxx Xxxxxx at TIPS at xxxx.xxxxxx@t xxx-xxx.xxx

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!