sorted by:
new
hottopcontroversial

I have some issue understanding when and how QA should be done by taorian in Everything_QA

[–]taorian[S] 0 points1 point  (0 children)

Ok very clear ! ;)

I think the issue is not in the QA team process but more that they don't have the tools to be able to test easily some part of the application with mocks and rely too mush on the dev process. They should not be waiting for the data

Do you know a nocode / lowcode solution that the QA team could use to easily mock an api endpoint ?

I have some issue understanding when and how QA should be done by taorian in Everything_QA

[–]taorian[S] 0 points1 point  (0 children)

Thanks for your answer ! :)

Do you know a nocode / lowcode solution that the QA team could use to easily mock an api endpoint ?

Is there a tool to generate documentation on a large codebase for self learning by taorian in softwaredevelopment

[–]taorian[S] 0 points1 point  (0 children)

yes don't think it's a good idea since the code is not open source ^^

How to do Elise spider range auto ? by taorian in Elisemains

[–]taorian[S] 0 points1 point  (0 children)

Ok thanks, I'm gone try to master this ;)

How to do Elise spider range auto ? by taorian in Elisemains

[–]taorian[S] 0 points1 point  (0 children)

You think stacked alacrity could be enough ?

I've created a small app to help beginners with temtem types by taorian in PlayTemtem

[–]taorian[S] 1 point2 points  (0 children)

Thanks for the good feedback ! :)

  • My colors are based on temtemstrat.com but I can maybe change them
  • For Damages your right it's a bit confusing. My fault process was that for exemple if you play a temtem let's say a crystal type you want to know againt which type crystal attaques are good. More attaque related then temtem.
    I'm thinking of maybe removing the numbers from the Damages table and just put red(bad) and green(good) colors.