-
Notifications
You must be signed in to change notification settings - Fork 124
beyond the UI #365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: gh-pages
Are you sure you want to change the base?
beyond the UI #365
Conversation
[like] Asrut Saha reacted to your message:
________________________________
From: Silas Benson ***@***.***>
Sent: Tuesday, September 30, 2025 10:26:46 AM
To: ScottLogic/blog ***@***.***>
Cc: Asrut Saha ***@***.***>; Author ***@***.***>
Subject: Re: [ScottLogic/blog] beyond the UI (PR #365)
@silasvb commented on this pull request.
________________________________
In _posts/2025-09-26-beyond-ui.markdown<#365 (comment)>:
+
+You discover bugs early—before they become expensive problems. You validate that your system can handle anything thrown at it, from perfect data to chaos. You run tests quickly and repeatedly, confident that your results are consistent and reliable.
+
+For example, you mock a `/api/ingest` endpoint that accepts regulatory data. You configure WireMock to return a `201 Created` response for valid data, a `400 Bad Request` for missing fields, and simulate a slow network by adding a delay for certain requests. You then run tests to check:
+
+- Does your system correctly process valid data?
+- Does it handle errors gracefully when data is incomplete?
+- Does it retry or timeout when the network is slow?
+
+WireMock becomes your safety net, letting you build and test with speed and confidence. When the real APIs finally become available, you’re ready—your system has already been battle-tested.
+
+## 6. Lessons for Every IT Enthusiast
+
+As the project wraps up, you realize you’ve learned something valuable. API testing and mocking aren’t just technical tricks—they’re essential strategies for building robust, scalable, and compliant systems. They let you move fast, catch problems early, and deliver quality software even when the pieces aren’t all in place.
+
+WireMock, in particular, stands out as a hero tool—giving you the power to simulate, test, and validate your APIs in any scenario.
Similar to my comment in Section 2, this is mixing API testing and Wiremock messages - I'd recommend this sentence is focused on Wiremock, e.g. ... and validate your system in any scenario, rather than API testing.
—
Reply to this email directly, view it on GitHub<#365 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBPF3ZNBE7DTQ6MDZI2ILRT3VJLGNAVCNFSM6AAAAACH4ADMV2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTEOBTHA2DAMJWHE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
The contents of this email and any attachments are intended solely for the addressee and may contain confidential or legally privileged information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. The information may not be used or disclosed except for the purpose for which it has been sent.
Email is susceptible to data corruption, interception, unauthorised amendment, viruses, and unforeseen delays. Although Scott Logic Limited has taken reasonable precautions to avoid these situations, it cannot accept responsibility for any loss or damage sustained as a result of any of these actions and the recipient must ensure that the email (and attachments) are virus-free.
Please note, that we do not accept notification of changes to bank account details by email. This applies to notifications from or to us.
Scott Logic Limited is a limited company registered in England and Wales with registration number 05377430. Registered office address: 6th Floor, The Lumen, St James Boulevard, Newcastle Helix, Newcastle upon Tyne, NE4 5BZ . Our VAT number is 866 1051 30.
|
[like] Asrut Saha reacted to your message:
________________________________
From: Silas Benson ***@***.***>
Sent: Tuesday, September 30, 2025 10:57:09 AM
To: ScottLogic/blog ***@***.***>
Cc: Asrut Saha ***@***.***>; Author ***@***.***>
Subject: Re: [ScottLogic/blog] beyond the UI (PR #365)
@silasvb commented on this pull request.
________________________________
In _posts/2025-09-26-beyond-ui.markdown<#365 (comment)>:
+
+Mocking lets you work in parallel—front-end and back-end teams can build and test without waiting for each other. You can simulate every scenario, from perfect data to the weirdest edge cases, and even inject errors or delays to see how your system reacts. It’s faster, cheaper, and gives you total control.
+
+## 4. Enter WireMock: The Hero Tool
+
+To bring this simulated world to life, your team chooses WireMock—a powerful open-source tool that acts as a stand-in for real APIs. WireMock lets you define exactly how your mock APIs should behave: what requests they accept, what responses they return, and how they handle errors or slowdowns.
+
+With WireMock, you can:
+
+- Create stubs for every endpoint your system needs.
+- Simulate successful data ingestion, error conditions, and even network timeouts.
+- Test your system’s resilience, error handling, and data validation—without ever touching the real APIs.
+
+## 5. The Project in Action
+
+Armed with WireMock, your team sets up mock endpoints for all the external data sources. You configure WireMock to send realistic regulatory data to your ingestion APIs, just like the real sources would. You test how your system handles valid data, invalid formats, missing fields, and unexpected errors.
This implies that Wiremock is acting as a controller, which it's not.
Also, this is inconsistent with how you describe the use of Wiremock immediately below, where you're discussing mocking content store rather than our external data providers - Which we didn't mock using Wiremock
—
Reply to this email directly, view it on GitHub<#365 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBPF3ZL56ACLQEBZOQRO4ZT3VJOYLAVCNFSM6AAAAACH4ADMV2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTEOBUGAYTENJSGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
The contents of this email and any attachments are intended solely for the addressee and may contain confidential or legally privileged information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. The information may not be used or disclosed except for the purpose for which it has been sent.
Email is susceptible to data corruption, interception, unauthorised amendment, viruses, and unforeseen delays. Although Scott Logic Limited has taken reasonable precautions to avoid these situations, it cannot accept responsibility for any loss or damage sustained as a result of any of these actions and the recipient must ensure that the email (and attachments) are virus-free.
Please note, that we do not accept notification of changes to bank account details by email. This applies to notifications from or to us.
Scott Logic Limited is a limited company registered in England and Wales with registration number 05377430. Registered office address: 6th Floor, The Lumen, St James Boulevard, Newcastle Helix, Newcastle upon Tyne, NE4 5BZ . Our VAT number is 866 1051 30.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this post is ready to publish as is, or if you're aiming it at the right target audience. In general we're trying to showcase Scott Logic's depth of tech knowledge and industry awareness. I don't think it really works either on that level or on the "article for beginners" level - it's a pretty high-level and light touch article which doesn't go deep enough into anything to showcase our expertise, and isn't explanatory enough to be any help in learning.
I'm not convinced there is enough material here to make a good post even with editing, so I've spoken around and asked Elliott Mason to reach out to you and discuss how you could find something interesting around this area to write about, and find an interesting aspect to your use of WireMock or the other work you did on the project, that would be worth writing about and would make for an engaging read
Ok Np. Thanks.
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Caitlin Salt ***@***.***>
Sent: Tuesday, September 30, 2025 3:13:57 PM
To: ScottLogic/blog ***@***.***>
Cc: Asrut Saha ***@***.***>; Author ***@***.***>
Subject: Re: [ScottLogic/blog] beyond the UI (PR #365)
@csalt-scottlogic requested changes on this pull request.
I'm not sure this post is ready to publish as is, or if you're aiming it at the right target audience. In general we're trying to showcase Scott Logic's depth of tech knowledge and industry awareness. I don't think it really works either on that level or on the "article for beginners" level - it's a pretty high-level and light touch article which doesn't go deep enough into anything to showcase our expertise, and isn't explanatory enough to be any help in learning.
I'm not convinced there is enough material here to make a good post even with editing, so I've spoken around and asked Elliott Mason to reach out to you and discuss how you could find something interesting around this area to write about, and find an interesting aspect to your use of WireMock or the other work you did on the project, that would be worth writing about and would make for an engaging read
—
Reply to this email directly, view it on GitHub<#365 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBPF3ZKIJEEH5ZQE4E2XRCD3VKF2LAVCNFSM6AAAAACH4ADMV2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTEOBVGEZTGOBWGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
The contents of this email and any attachments are intended solely for the addressee and may contain confidential or legally privileged information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. The information may not be used or disclosed except for the purpose for which it has been sent.
Email is susceptible to data corruption, interception, unauthorised amendment, viruses, and unforeseen delays. Although Scott Logic Limited has taken reasonable precautions to avoid these situations, it cannot accept responsibility for any loss or damage sustained as a result of any of these actions and the recipient must ensure that the email (and attachments) are virus-free.
Please note, that we do not accept notification of changes to bank account details by email. This applies to notifications from or to us.
Scott Logic Limited is a limited company registered in England and Wales with registration number 05377430. Registered office address: 6th Floor, The Lumen, St James Boulevard, Newcastle Helix, Newcastle upon Tyne, NE4 5BZ . Our VAT number is 866 1051 30.
|
Have you (please tick each box to show completion):
npm install
followed bynpx mdspell "**/{FILE_NAME}.md" --en-gb -a -n -x -t
if that's your thing)Posts are reviewed / approved by your Regional Tech Lead.