Skip to main content

Tester's Choice

Search This Blog

כאן תמצאו ראיונות שערכתי עם מנהלי בדיקות כפי שפורסמו במגזין "עולם הבדיקות"

Get link
Facebook
X
Pinterest
Email
Other Apps

ארנון אקסלרוד, יועץ אוטומציה

עמית גדול, צ'ק פוינט

חן חליו, הפניקס

לנה כץ, Gett

יוג'ין ליבוביץ, Live Person

אייל אזולאי, ורינט

שגיא וכמן Glide

מירום לורנץ, Wirecard

ערן דמלין, בנק אגוד

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Post a Comment

Archive

March 202460

Popular Posts

What are the biggest challenges in software testing today? We've asked chatGPT

His answer: Keeping up with new technologies and changes in the software development landscape. Ensuring comprehensive testing coverage for complex and dynamic systems. Managing and automating the testing process to increase efficiency and reduce costs. Managing and preventing bugs and defects in software. Ensuring compatibility and usability across different platforms and devices. Managing and analyzing large amounts of data generated during testing. Managing and coordinating testing across different teams and departments. Ensuring security and privacy of data during testing. Managing and preventing human errors in testing. Keeping up with changing customer and user needs and expectations. **I can think of a few more, but I agree with chatGPT. original publication: Jan 20, 2023

Cloning XRAY issues - what to expect (Jira server)

This time, most of the post content is copied from XRAY. The idea is to have all clone behavior in one location and not per issue type, as in XRAY site. Test Plan (and respective Board) The new Test Plan will be created in a clean state, containing the original Tests without any execution related information. If hierarchical test organization, the Board folder structure is also cloned . Example: Original: Cloned: Test Execution When cloning a Test Execution issue, all the Test issue associations will also be cloned . However, a new Test Run is created for each Test so that the new Test Execution issue has no execution state . Also: If the test execution contains links to another issue (s), you can select whether or not to include the links in the new clone test execution. If the test execution contains sub-tasks, you can select whether or not to create the sub-tasks in the new clone test execution. If the test execution contains attachments, you can select whether or not to include

XRAY: explaining the (complex) relations between Test Plans, Tests, and Test Executions

Have you heard about the synch between Test Plans (TP) and Test Executions (TE)? Don’t feel bad if you didn’t – there isn’t any. Not full synch in any case. This can be very confusing and important to understand in regard to data integrity. What to do to avoid data integrity issues? Verify that all the tests in the test section of the TP are also embedded in TE in the same TP. If all TE tests run (Pass, Failed, etc., not in TODO) you will see unlinked tests in the TP as TODO. In the TP choose Create Test Execution=>with Status=>TODO and run them in the new TE. Verify that Tests appear only in one TE associated with the same TP. If you remove TE from a TP because it is not relevant, you need to manually remove the tests in the TP. Also important: Test executions are in context to TP: only results from the embedded TE will be seen in the TP. Test X Failed, ran again later, and passed. If the Fail is n a TE linked to a TP and the same test passed in a different TE, the TP will sh

Powered by Blogger