What are best practices for testing iot edge code?
Actually there are several questions, i'm struggling now
How to unit test iot edge module code?
How to test the code on a device esp. message routing etc.?
Struggling with this topics. I have angular backbground - testing is a concept by design.
It seems for me that testing is not a key concept on iot devices.
Does somebody has experince on that?
Related
good afternoon
I am reviewing the concepts of SOA and I have this question.
SOA-> COVERS in 2 technologies, SOAP(xml) AND REST(xml,json,txt,etc)
Microservices that is based on SOA, uses SOAP or is only based on REST?
obs: if it is clear that the microservice goes by the level of decoupling, independence and only specific tasks, but my question is if I can have microservices based on SOAP?
I have read a lot of documentation, I have that doubt.
Thanks a lot.
Microservices are more of a concept/software architecture style where you have independently and scalable services.
If your organisation/project requires soap protocol (which often happens in legacy projects when you want to switch from soa to microservces) you can also do microservices with it.
I've been using AWS appsync service. However, I'm not able to figure out a way to write unit test cases for the development I've been doing.
Please see if anyone can share any information in this regard.
Was just listening to Josh Suereth's talk "Introduction to Actors Systems" on Devnexus 2013 and got excited. I am familiar with Enterprise Integration Patterns and have Spring Integration experience.
What benefits can Akka provide that Spring Integration can't handle?
Are they competitors or is there any use case where I would like to integrate them?
Thank you for your feeadback on the matter, first of all!
I'm not familiar with Akka and really not sure it does. Seems for me it is something similar what we have with Reactor.
From other side, if you familiar with Akka and with Spring Integration as well, the contribution is always welcome. We have an Extension Repo, where you can start a new project on the matter and we will follow with you PoC and go ahead with robust integration.
From other side I know that Apache Cammel has Akka extension (http://doc.akka.io/docs/akka/current/java/camel.html), so I don't see reason don't not support it from Spring Integration as well.
Yes, I haven't answered for your original question, but as I know no one from our team is familar with Akka.
Hope someone else share his wisdom here.
Does anyone have any opinions on how TDD and UNIT testing would would when developing web services using Oracle Service Bus? All I can think of is stubbing out the back ends then running tests through the service bus, but that's really just integration testing. How would I apply TDD principles in this instance?
Is your question actually how best to conduct unit tests on Oracle Service Bus components? I have the same issue but have come to the view that now your unit of code is not a Java method or a class but a whole proxy.
It does however limit you to being only able, at best, to conduct component integration testing as you have described: Stubbing out the other systems and running what you'd traditionally call Integration tests through the Service Bus.
Scale up your unit of work.
If there is a better way to automate and test these code artifacts then I want to hear about it.
We have a requirement at my workplace to automate the webservice testing. We have been using QTP scripts to do so.
We as a team, Kind of leaning towards Jbehave as a choice. Is JBehave a good choice for web service functional testing automation?
We do use Soap UI to test manually. But we are planning to automate the functional and regression testing to reduce the release cycle time.
Suggestions welcome.
It may not be possible easy to implement load (performance) tests. Can't see any reason why writing functional and regression tests would be a problem.