Software testing Implementation

Software testing Implementation

• The testing process

• Test case design

• Automated testing

• Alpha and beta site testing programs

The planning activities include:

• Determining the test methodology

• Planning unit and integration tests

• Planning the system test

• Designing the tests.

Determining the test methodology

• berkaitan dengan keputusan tentang standar kualitas perangkat lunak yang diperlukan dan pengujian menyeluruh atau pengujian tambahan (bottom-up atau top-down), dan sejauh mana pengujian otomatis

Planning unit and integration tests

• Prior to planning the tests, preferences must be established as to which unit and integration test will be carried out, based on the system’s characteristics.

Planning the system test

Planners focus on the following main issues:

• What to test?

• Which types of sources are to provide the test cases?

• Who performs the tests?

• Where will the tests be performed?

• When to terminate the tests?

Designing the test

The products of the test design stage are:

• Detailed design and procedure for each test,

• Test case database/file.

There are basically two types of test case sources:

• Random samples of real-life cases

• Synthetic test cases (“simulated test cases”) prepared by the test designers.

Automated Testing

• Code auditors.

• Coverage monitors.

• Functional tests.

• Load tests.

• Test management.

The main advantages of automated tests are:

• Accuracy and completeness of performance

• Accuracy of results log and summary reports

• Ability to obtain much more comprehensive information

• Performance requires few manpower resources

• Shorter testing periods

• Performance of complete regression tests

• Performance of test classes beyond the reach of manual testing.

The main disadvantages of automated tests are:

• High investments required in package purchasing and training

• High manpower tester resources for preparing the tests

• Considerable testing areas not covered by automated testing.

Testing Alpha dan Beta

• Metode pengujian yang dilakukan dengan cara melibatkan pengguna akhir potensial dari program yang dibangun

Keunggulan pengujian beta

■ Identifikasi kesalahan tak terduga

■ Luas lingkup cakupan dalam pencarian kesalahan

■ Biaya rendah

Kelemahan pengujian beta

■ Sistematika pengujian kurang

■ Kesalahan laporan kualitas rendah

■ Banyak usaha manusia dikeluarkan untuk memeriksa laporan peserta

Kesimpulan

• Implementasi pengujian : melaksanakan pengujian berdasarkan pelakuknya dan tahapan pengembangan sistem

• Jenis testing : alpha (developer) dan beta (user/pihak eksternal)

• Perlu dibuatkan rencana testing: siapa, apa, dimana, kapan, yang mana, dan bagaimana

• Strategi pengujian:

– Metodelogi : big bang (menyeluruh) incremental (bertahap:detail to global dan global to detail)

– Tehnik tool: black box dan white box

• Black boxlebih sering dilakukan

dilakukan pada saat exekusi program

dilakukan oleh developer

• White boxSDM khusus;

syarat:ada source code

• Kedua jenis test ini sangat diperlukan dan saling melengkapi