Lucent IT Services

We offer software testing services, specialising in API and automated testing.
We think we can help get your products tested, get in touch!

[Lucent IT Services @LucentItSvs]

@ministryoftest Play guitar (badly).

[Lucent IT Services @LucentItSvs]

I have to look through some log files, but they’re too big for text editors. Found this on SO and I can’t believe I didn’t found out sooner… https://t.co/Y9Crmps80I

[Lucent IT Services @LucentItSvs]

@ministryoftest For a release we write a Test Plan, which includes a high-level test approach and the tools we’re going to use.

[Lucent IT Services @LucentItSvs]

@ministryoftest ReadyAPI. Big fan of this tool. Also have used Postman to a lesser extent.

[Lucent IT Services @LucentItSvs]

@villabone @gear4music Guitars AND testing? Nice one!

[Lucent IT Services @LucentItSvs]

@ministryoftest Performance, resilience, backups....

[Lucent IT Services @LucentItSvs]

@ministryoftest

[Lucent IT Services @LucentItSvs]

@DanAshby04 That said, it is good to see that over the past decade, things have improved immensely.

[Lucent IT Services @LucentItSvs]

@DanAshby04 Right of the start of my career, testers were always seen as lower-skilled and a lesser role in comparison to development. E.g. those who can’t write code; test. Why? I dunno, snobbery perhaps.

[Lucent IT Services @LucentItSvs]

@ministryoftest Simply put, move more.

[Lucent IT Services @LucentItSvs]

@tlakomy @bahmutov Currently E2E.

[Lucent IT Services @LucentItSvs]

@ministryoftest Carefully! Usually performance tests during quiet periods after deploying a new build or some change to a dependent component.

[Lucent IT Services @LucentItSvs]

@ministryoftest Java, JavaScript and Groovy on a daily-ish basis.

[Lucent IT Services @LucentItSvs]

@Stephen346 @ministryoftest Agreed. Depends on what you’re testing. Data driven? 1000’s. Manual could be a couple of hundred or even tens depending on test cases. I suppose a better question might be, how quickly can you run full suite of regression without obstacles.

[Lucent IT Services @LucentItSvs]

@ministryoftest I have a early “test” stack will minimal data that I can refresh to known state. I have another stack (not using env names to save arguments) which is about 90-95% match to prod in terms of data and configuration.

[Lucent IT Services @LucentItSvs]

@ministryoftest I also verify in Production out of hours to be sure.

[Lucent IT Services @LucentItSvs]

@ministryoftest Yep. Regularly check and record performance of a particular web service, with increasingly larger payloads, against previous results to look for decrease in response times. Aim to ensure that new builds don’t impact performance. If it does, we don’t go live.

[Lucent IT Services @LucentItSvs]

Just stumbled onto @smashtestio today. Looks really neat and will be giving a go to automate UI tests for my current project.

[Lucent IT Services @LucentItSvs]

@parceljs was a breeze to set up. No config, no piping or chaining commands. Absolute doodle and will be keeping it in for this project.

[Lucent IT Services @LucentItSvs]

I’ve previously used Babel/Weback for React builds and thinking of trying @parceljs for my next project. Anyone got any advice or gotchas to be aware of?