smoke-testing

I need to write a smoke test in Java which validates whether the system is connected to kafka, Does anyone have any idea? I have found this post: How to check whether Kafka Server is running? But it's too complicated to do from a Java code and I don't think It's the direction i should use. Thanks in advance. I had the same question and I don't want to leave this question without any answer. I read a lot about how I can check the connection and most of the answers I found was checking the connection with Zk, but I really want to check the connection directly with Kafka server. What I did is to

After I deploy a build to staging. I would like to have a system that smoke tests all our webpages looking for error http status codes (400,500). What is the easiest, fastest way to get a system like this into place. If I use selenium or WebAII it seems like I'd have to do alot of work generating basic unit tests. Ideally Id like to be able to autogenerate a dead simple test for all my page, then over time build some more interactive UI tests. I dont really want to roll my own solution using wget or something. I'd appreciate some suggestions. Thanks Ideally Id like to be able to auto-generate

I was taught that a regression test was a small (only enough to prove you didn't break anything with the introduction of a change or new modules) sample of the overall tests. However, this article by Ron Morrison and Grady Booch makes me think differently: The desired strategy would be to bring each unit in one at a time, perform an extensive regression test, correct any defects and then proceed to the next unit. The same document also says: As soon as a small number of units are added, a test version is generated and "smoke tested," wherein a small number of tests are run to gain confidence

What is it and why is it used/useful? A sanity test isn't limited in any way to the context of programming or software engineering. A sanity test is just a casual term to mean that you're testing/confirming/validating something that should follow very clear and simple logic. It's asking someone else to confirm that you are not insane and that what seems to make sense to you also makes sense to them... or did you down way too many energy drinks in the last 4 hours to maintain sanity? If you're bashing your head on the wall completely at a loss as to why something very simple isn't working...

I thought I understood that a smoke server was used for continous integration to measure the performance and test coverage of a project. Is this basically correct? What does it mean to smoke-test a program? Does it simply mean to continously apply the tests defined on the smoke server to be able to pinpoint performance degradation to a particular time frame? Smoke testing is a set of basic cheap to run tests that precede actual testing. It aims to verify that the build is deployed successfully and that all test env. aspects are running and ready for the actual test process. It saves you