Test the current wallet app features in dev env. (the newest one is: share token)
FYI, here is a spec of how to test app:
• For an Application, we use BDD to define feature and implement e2e test, for new Pull Request, an e2e test runs and checks the code, (and report the error if any)
• When merge to master, also trigger a e2e test, and create the test report and video, then upload/commit to the master.
• Set up the publisher for the test report and video, so anyone can check the current test result and demo video( visibility)
• Also, new code is deployed to dev env.
• The QA engineer use the BDD, the test result and video as the reference to start testing the app
• When QA engineer find bugs, report issue with the BDD language (the similar way as we do to describe the feature)
• Then developer confirm the bug and fix it, developer can decide that for some important scenario reported by this bug it is necessary to implement the BDD test in the BDD feature, so: it become a feature specification, and can be protected by test.
• QA engineer trace the issue till it is finally fixed.
Test the current wallet app features in dev env. (the newest one is: share token)
FYI, here is a spec of how to test app:
• For an Application, we use BDD to define feature and implement e2e test, for new Pull Request, an e2e test runs and checks the code, (and report the error if any)
• When merge to master, also trigger a e2e test, and create the test report and video, then upload/commit to the master.
• Set up the publisher for the test report and video, so anyone can check the current test result and demo video( visibility)
• Also, new code is deployed to dev env.
• The QA engineer use the BDD, the test result and video as the reference to start testing the app
• When QA engineer find bugs, report issue with the BDD language (the similar way as we do to describe the feature)
• Then developer confirm the bug and fix it, developer can decide that for some important scenario reported by this bug it is necessary to implement the BDD test in the BDD feature, so: it become a feature specification, and can be protected by test.
• QA engineer trace the issue till it is finally fixed.