what is Smoke testing

inhousetrainer.net :

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

via Blogger https://ift.tt/2QUQOfn
what is Smoke testing
Mr. Hery Purnama – Trainer – 081223344506

Training MS. Access Database Fundamental – Monotaro Jakarta

inhousetrainer.net :

Inhouse training MS. Access database fundamental di PT. Monotaro Indonesia – Sudirman Jakarta, terima kasih atas undangan dan partisipasinya, semoga bermanfaat.
Hery Purnama
Freelance Trainer

via Blogger https://ift.tt/2y7kv5C
Training MS. Access Database Fundamental – Monotaro Jakarta
Mr. Hery Purnama – Trainer – 081223344506

Silabus Training DevOps (Development and Operations)

inhousetrainer.net :

Silabus Devops
5 Days (09.00 – 16.00)
You will learn how to improve the Software Development Lifecycle by applying techniques to improve software delivery. The training  will explain how to improve delivery using automation, configuration management, provisioning and deployment tools. It  also cover newer tools like Docker and Kubernetes. Where possible the trainer will point you towards the best practices in the field.
What are the requirements?
Understanding the basics of networking and be able to write code in any programming language will significantly increase your course experience
If you are not familiar with the basic system administration concepts, you might have to do some additional reading. You can also use our discussion board to ask questions if something is unclear.
What am I going to get from this course?
Apply DevOps in your team
Understand Continuous Delivery
Automate the Software Development Lifecycle (SDLC)
Automate the deployment process
Reduce release time
Release better software
Build a highly available and fully scalable application
Deploy microservices using Docker and Kubernetes
Automate using Ansible and Chef
What is the target audience?
This course is suitable for System Administrators, Developers, IT Managers, IT Operations team members, who want to learn more about DevOps. If you are not exposed to software delivery, this course might not be suitable for you.
 Getting Started – DevOps Concepts, Tools, and Technologies  
Understanding the DevOps movement
DevOps with the changing times
The waterfall model
The agile model
Cloud computing – the disruptive innovation
Why DevOps?
The benefits of DevOps, CALMS
The DevOps lifecycle – it's all about “continuous”
Build automation
Continuous integration
Best practices
Cloud computing
Configuration management
Continuous delivery/continuous deployment
Best practices for continuous delivery
Continuous monitoring
Continuous feedback
Tools and technologies
Code repositories – Git
Differences between SVN and Git
Build tools – Maven
Example pom.xml file
Continuous integration tools – Jenkins
Key features and benefits
Configuration management tools – Chef
Cloud service providers
Container technology
Monitoring tools
Deployment orchestration/continuous delivery – Jenkins
End-to-end orchestration: Jenkins plugins
The DevOps dashboard
An overview of a sample Java EE application
The list of tasks
 Continuous Integration with Jenkins
Installing Jenkins
Setting up Jenkins
The Jenkins dashboard
Configuring Java and Maven in Jenkins