MockServer Component Testing
The testing struggle is real…
We test complex systems that integrate with multiple other complex systems.
These kinds of dependencies can cause inevitable delays on getting testing done. However working in a micro services environment this requires testing sooner to deliver faster.
To assist us with this problem we use MockServer to mock out some of the systems we integrate with via HTTP or HTTPS.
Using MockServer allows us to do a couple of really cool things like:
· Create the responses for our HTTP dependencies.
· Isolate the SUT so we remain in a known state.
· Test the application in isolation and not all its other dependencies.
· Include test assertions that verify the requests the SUT has sent.
Come hear about some of the testing problems we faced and how MockServer helped us on our Automation testing journey.
Outline/structure of the Session
PowerPoint presentation - introduction of ourselves and a brief explanation of what MockServer is.
Workshop - which will include a demo and practical application of how to use MockServer to mock dependencies.
Learning Outcome
How mock-server works
Collaboration effort for devs and testers
Mocking dependencies & verify requests
Test sooner & deliver faster
Isolating the SUT
Target Audience
Developers and Testers
Prerequisite
Laptops
Chargers
Notebook and pen
A smile
Good energy
Links
This is a new talk which we have not presented yet.
schedule Submitted 3 weeks ago
Recent Activities
- reply Calvin Moore replied "Apologies - commented." on the comment Hi Blanche, Calvin, Can y...schedule 1 week ago
- reply Calvin Moore replied "Our sincerest apologies f..." on the comment Hi Blanche, Calvin, MockS...schedule 1 week ago
- reply Naresh Jain replied "Hi Blanche, Calvin, Can y..." on a comment on proposal MockServer Component Test...schedule 1 week ago
Call for Proposals 3 days left
Submit before Dec 15 '18 10:16 AM IST
We are looking for deep technical topics related to Appium and testing in general. We are committed to diversity and believe in transparency. Hence, all proposals will be public.
Registered user will be able to comment on your proposal. You are required to reply to those comments to provide clarifications, explain revisions and respond to questions. The program team will look at how well you've responded to comments and updated your proposal to incorporate public suggestions. Ultimately the decision to accept a session resides with the program team.
Your proposal stands the best chance to be selected, if it's unique, fully flushed, ready-to-go. Please ensure you've read:
To encourage early submissions and iterative improvement of proposals, we start accepting proposals as soon as we find them a good fit. Since competition gets tougher with progressing time, it is advisable to avoid waiting until the last minute for proposal submission.
Comments
Hi Blanche, Calvin,
MockServer component testing seems very relevant. However, how would you make this topic fit / tie with AppiumConf?
Also, can you share some reference slides & a sample video of you speaking about the content to help the program team?
Hi Blanche, Calvin,
Can you please reply to Anand's comments?
Apologies - commented.
Our sincerest apologies for the delayed response. I have been out of the office for 3 weeks, only returning to work today.
We feel our proposal is relevant as its both technical and relates to testing which has been indicated as topics of interest.
In addition, we believe attendees stand to gain valuable insights to assist them with their automation strategies which is aligned with the purpose of the Appium Conf.
Component testing is a formalised way of testing systems. Any decent testing pyramid schematic has featured it for the last few years and has sound theoretical backing. However, implementing it in a real world scenario and gaining significant benefit to offset the additional cost of development is an entirely different story. We would like to share our learnings with your audience having invested many man months into this project. We aim to describe the problem we are looking to solve in a way that is relatable to many dev houses, how we went about implementing it, its shortcomings, our learnings, and its return on investment for teams in our company that are actively using it. And finally, we will discuss our planned next steps and how we will use this newly developed design as a stepping stone to automated cross system end to end tests in spawned environments.
Regards
Calvin & Blanché