PT. HM. SAMPOERNA, Tbk. - Pasuruan Jawa Timur

Inhouse Training Microsoft Excel VBA Macro Programming


Inhouse Training Android Apps. Development with phonegap

O-Shop, SCTV, Infotech (Jakarta)

Public Training Magento E-Commerce Advanced Level


Training IT Project Management based on PMBOK 5

Bank Fama International - Bandung

Inhouse Training Open Office Calc

Tuesday, October 23, 2018

Trainer Project Management Jakarta

Sesi Group Discussion training project management dengan peserta dari direktorat pajak. Terima kasih kepada sciencom atas undangan mengajar topik Project Management based on PMBOK

Semoga bermanfaat

Hery Purnama
Project management trainer
PMBOK Trainer

Training Spark Developer for bigdata

Training Apache Spark Developer Batch 1 bersama 17 peserta dari EBdesk bintaro, terima kasih atas undangan mengajar dan semoga bermanfaat


Hery Purnama
Apache Spark Trainer
Hadoop Bigdata Trainer

Trainer training CTFL software testing ISTQB bandung

Terima kasih atas undangan mengajar CTFL dari Badan Siber Sandi Negara BSSN dan vendor sciencom semoga materi software testing foundation bermanfaat.


Hery Purnama
Software Testing Trainer 

Monday, October 15, 2018

what is Smoke testing

Smoke Testing Explanation

In computer programming and software testing, smoke testing (also confidence testing, sanity testing, build verification test (BVT) and build acceptance test) is preliminary testing to reveal simple failures severe enough to, for example, reject a prospective software release

SMOKE TESTING, also known as "Build Verification Testing", is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing.

The term 'smoke testing', it is said, came to software testing from a similar type of hardware testing, in which the device passed the test if it did not catch fire (or smoked) the first time it was turned on.

Smoke Testing

Smoke testing covers most of the major functions of the software but none of them in depth. The result of this test is used to decide whether to proceed with further testing. If the smoke test passes, go ahead with further testing. If it fails, halt further tests and ask for a new build with the required fixes. If an application is badly broken, detailed testing might be a waste of time and effort.

Smoke test helps in exposing integration and major problems early in the cycle. It can be conducted on both newly created software and enhanced software. Smoke test is performed manually or with the help of automation tools/scripts. If builds are prepared frequently, it is best to automate smoke testing.

As and when an application becomes mature, with addition of more functionalities etc, the smoke test needs to be made more expansive. Sometimes, it takes just one incorrect character in the code to render an entire application useless.

    It exposes integration issues.
    It uncovers problems early.
    It provides some level of confidence that changes to the software have not adversely affected major areas (the areas covered by smoke testing, of course)


Smoke testing is normally used in Integration Testing, System Testing and Acceptance Testing levels.

Do not consider smoke testing to be a substitute of functional/regression testing

Sunday, October 7, 2018

Training MS. Access Database Fundamental - Monotaro Jakarta

Inhouse training MS. Access database fundamental di PT. Monotaro Indonesia - Sudirman Jakarta, terima kasih atas undangan dan partisipasinya, semoga bermanfaat.


Hery Purnama
Freelance Trainer