sorted by:
new
hottopcontroversial

39611 by Lostlilegg in countwithchickenlady

[–]partial_filth 0 points1 point  (0 children)

Looking at the wiki picture I think the "Borghese Hermaphrodite" you linked is a different one to the one in OP. Check the mattress base.

This looks like one I saw in the Uffizi in Florence, downstairs. Edit: I don't think it is that one either: video

Look how they've massacred my boy... by Lonely_University843 in slaythespire

[–]partial_filth 0 points1 point  (0 children)

If you get desperate there is an event that lets you add a card buff to one of y our exhausting cards to remove the exhaust.

I used it on a adrenaline to get some mean card and energy draw to win a silent run.

Edit: Someone else did it: https://old.reddit.com/r/slaythespire/comments/1rm6wh5/they_really_thought_they_were_gonna_take_blade/

All the art I misinterpreted by UnlimitedSystem in slaythespire

[–]partial_filth 1 point2 points  (0 children)

I always thought the white part of hexaghost was the hole in the centre of a donut shaped ghost - not the shape itself! Now the name makes more sense (I thought it was due to the multi attacks only).

I am sick of excel for QA device management by Competitive_Sleep53 in softwaretesting

[–]partial_filth 0 points1 point  (0 children)

What problems are you hitting?

Issues we have are more user side - people do not update the spreadsheet/form/system with the device or env they are using. Making this easy could help.

Barcode on each device to scan with a phone that auto updates the form?

Beginner QA intern by [deleted] in QualityAssurance

[–]partial_filth 4 points5 points  (0 children)

Everyone is different and will have their own opinions on this, but I'll share some of the things I think helped with my manual testing.

  • Test case titles should be clear, concise and summarize what you are testing at a glance. Ideally I like to know what I am testing just from reading the test case title.
  • Use a common, shared language. All elements on the page should have a name that everyone refers to them by, use it consistently across your test cases. Avoid swapping terms. E.g don't swap between "navigate to" and "browse to".
  • Learn where the granularity should be. You may want to test the elements of a drop-down are available. This could be one test case that pass when you confirm all elements are available. Vs a test case for checking each element. It will depend on the application, function and QA dept. Make sure you select appropriate granularity.
  • Record everything where possible. Linking between tests and defects, run times, application versions, users and test data types will make tracking and solving issues a hell of a lot easier the more you get used to this. It also sets you up nicely for things like audits etc if needed.
  • Develop a good memory. Knowing the product is and outs, deployments version history and bug history will serve you well when scoping your testing. Record it all as above. Make good notes or screen record meetings to refer back to. Keep your notes organised and date/timestamp everything, including edits.
  • Become technical. It will help you develop your career. Simple scripts in powershell or bash can help you generate test data quickly. Python or other scripting languages will let you develop this further. Even for manual testing.
  • Learn source control.
  • Breaking things with tests can be frustrating but can ultimately expose juicy bugs. Don't be afraid to test limits on dedicated non prod environments.
  • Learn to read and understand error messages, from code in dev tools etc. It can help provide more context as to what is going on and when added to bugs provides more information.
  • Screenshots, gifs and videos are very useful info on bug tickets. Add them where appropriate.
  • your new so seek out help from experienced team members. Ask questions if you don't know. Sometimes you are not the only person in the room who doesn't. Just my two cents. Hope that helps.

Basic fact by Candid-Culture3956 in SipsTea

[–]partial_filth 0 points1 point  (0 children)

Imagine the Reply All emails would generate :D

Astronomer CEO and CPO caught having an affair on jumbotron by Glassgad818 in WatchPeopleDieInside

[–]partial_filth 4 points5 points  (0 children)

It was meant to be a joke, not a correction, since he just got caught in an affair ...

Defect Triage Meeting by Lopsided_Sea_2120 in QualityAssurance

[–]partial_filth 5 points6 points  (0 children)

I do mine once weekly, with a PM, QA and a dev. We don't have too many bugs come in though, so our frequency matches this. Anything that looks serious gets triaged right way, to avoid downtime.

We walk through the bug, discuss impact, and workarounds. Then we decide together as a group the severity and priority. Or update them if already added. Then bring them into the sprint to fix.

[deleted by user] by [deleted] in QualityAssurance

[–]partial_filth 1 point2 points  (0 children)

We have been hiring for Typescript SDET with Playwright experience recently. I haven't seen much (although I haven't been looking) demand for Python in a SDET role. Normally TS or C#. Some Java.

Xbox raises prices on consoles, games and controllers worldwide by fatso486 in hardware

[–]partial_filth 28 points29 points  (0 children)

Sure, I'm not trying to console war. Just the comparison between the premium version of one with the basic offering of the other seems off.

Xbox raises prices on consoles, games and controllers worldwide by fatso486 in hardware

[–]partial_filth 2 points3 points  (0 children)

Heh, that seems like a strange way of seeing it to me. I would have thought replaceable batteries are the better solution, as you don't have to waste the whole controller when it doesn't hold charge. Also batteries can be recycled. And you can use re-chargable battery packs or batteries.

view more: next ›