Smoke Tests: These are tests which try to simulate what happens when
stuff is hitting the fan; that is to say, in actual service.
These tests cover every user-accessible or client-accessible control
or API, every use-case, and (in the case of UI testing) they do so
in an unpredictable but legitimate sequence.
(Some pretentious typography elided).
Do you have a reference that supports your definition of smoke test?
From Smoke testing (wikipedia):
In computer programming and software testing, smoke testing is a
preliminary to further testing, intended to reveal simple failures
severe enough to reject a prospective software release.
From stack overflow question
Smoke test: A simple integration test where we just check that when the
system under test is invoked it returns normally and does not blow up.
It is an analogy with electronics, where the first test occurs
when powering up a circuit: if it smokes, it's bad.
Smoke testing is non-exhaustive software testing, ascertaining that the most
crucial functions of a program work, but not bothering with finer details.
Update: some more definitions from the
stack overflow question:
Smoke testing: first tests on which testers can conclude if they will continue testing.
Smoke testing is done as a quick test to make sure everything looks okay before you get involved in the more vigorous testing.